Skip to main content
Glama
Salesforce MCP Server

Salesforce MCP Server

by tsmztech

Salesforce MCP 서버

Claude와 Salesforce를 통합하는 MCP(Model Context Protocol) 서버 구현으로, Salesforce 데이터 및 메타데이터와 자연어 상호작용을 지원합니다. 이 서버를 통해 Claude는 일상적인 언어를 사용하여 Salesforce 객체와 레코드를 쿼리, 수정 및 관리할 수 있습니다.

특징

  • 개체 및 필드 관리 : 자연어를 사용하여 사용자 정의 개체 및 필드를 만들고 수정합니다.

  • 스마트 개체 검색 : 부분 이름 일치를 사용하여 Salesforce 개체 찾기

  • 자세한 스키마 정보 : 모든 개체에 대한 포괄적인 필드 및 관계 세부 정보를 얻으세요.

  • 유연한 데이터 쿼리 : 관계 지원 및 복잡한 필터를 사용한 레코드 쿼리

  • 데이터 조작 : 레코드를 쉽게 삽입, 업데이트, 삭제 및 업서트합니다.

  • 객체 간 검색 : SOSL을 사용하여 여러 객체에서 검색

  • Apex 코드 관리 : Apex 클래스 및 트리거 읽기, 생성 및 업데이트

  • 직관적인 오류 처리 : Salesforce 관련 오류 세부 정보를 통한 명확한 피드백

Related MCP server: Salesforce MCP Server

설치

지엑스피1

도구

세일즈포스 검색 객체

표준 및 사용자 정의 개체 검색:

  • 부분 이름 일치로 검색

  • 표준 및 사용자 정의 객체를 모두 찾습니다.

  • 예: "계정과 관련된 개체 찾기"는 Account, AccountHistory 등을 찾습니다.

salesforce_describe_object

자세한 개체 스키마 정보를 얻으세요:

  • 필드 정의 및 속성

  • 관계 세부 정보

  • 선택 목록 값

  • 예: "계정 개체의 모든 필드를 보여주세요"

세일즈포스 쿼리 레코드

관계 지원을 사용한 쿼리 레코드:

  • 부모와 자녀의 관계

  • 자녀와 부모의 관계

  • 복잡한 WHERE 조건

  • 예: "관련 연락처가 있는 모든 계정 가져오기"

세일즈포스_dml_레코드

데이터 작업 수행:

  • 새 레코드 삽입

  • 기존 레코드 업데이트

  • 기록 삭제

  • 외부 ID를 사용하여 Upsert

  • 예: "여러 계정의 상태 업데이트"

세일즈포스 관리 객체

사용자 정의 객체를 만들고 수정합니다.

  • 새로운 사용자 정의 객체 만들기

  • 객체 속성 업데이트

  • 공유 설정 구성

  • 예: "고객 피드백 객체 만들기"

세일즈포스 관리 필드

개체 필드 관리:

  • 새로운 사용자 정의 필드 추가

  • 필드 속성 수정

  • 관계를 만들어라

  • 예: "계정에 평가 선택 목록 필드 추가"

세일즈포스_검색_모두

여러 객체 검색:

  • SOSL 기반 검색

  • 다중 객체 지원

  • 필드 스니펫

  • 예: "계정 및 기회에서 '클라우드' 검색"

세일즈포스_리드_에이펙스

Apex 수업 읽기:

  • 특정 클래스의 전체 소스 코드를 얻으세요

  • 이름 패턴과 일치하는 클래스 나열

  • 클래스 메타데이터(API 버전, 상태 등) 보기

  • 이름 패턴에서 와일드카드(* 및 ?) 지원

  • 예: "AccountController 클래스를 보여주세요" 또는 "Account Cont 와 일치하는 모든 클래스를 찾으세요"

세일즈포스_라이트_에이펙스

Apex 클래스를 만들고 업데이트합니다.

  • 새로운 Apex 클래스 만들기

  • 기존 클래스 구현 업데이트

  • API 버전 지정

  • 예: "계정 작업을 처리하기 위한 새로운 Apex 클래스 만들기"

세일즈포스_리드_에이펙스_트리거

Apex 트리거 읽기:

  • 특정 트리거의 전체 소스 코드를 얻으세요

  • 이름 패턴과 일치하는 트리거 목록

  • 트리거 메타데이터(API 버전, 개체, 상태 등) 보기

  • 이름 패턴에서 와일드카드(* 및 ?) 지원

  • 예: "AccountTrigger 표시" 또는 "연락처 개체에 대한 모든 트리거 찾기"

세일즈포스_쓰기_에이펙스_트리거

Apex 트리거를 만들고 업데이트합니다.

  • 특정 개체에 대한 새로운 Apex 트리거 만들기

  • 기존 트리거 구현 업데이트

  • API 버전 및 이벤트 작업 지정

  • 예: "계정 개체에 대한 새 트리거 만들기" 또는 "리드 트리거 업데이트"

salesforce_execute_anonymous

익명의 Apex 코드 실행:

  • 영구 클래스를 생성하지 않고 Apex 코드 실행

  • 디버그 로그 및 실행 결과 보기

  • 다른 도구에서 직접 지원하지 않는 데이터 작업에 유용합니다.

  • 예: "계정 메트릭을 계산하기 위해 Apex 코드 실행" 또는 "관련 레코드를 업데이트하기 위한 스크립트 실행"

세일즈포스 관리 디버그 로그

Salesforce 사용자의 디버그 로그 관리:

  • 특정 사용자에 대한 디버그 로그 활성화

  • 활성 디버그 로그 구성 비활성화

  • 디버그 로그 검색 및 보기

  • 로그 수준 구성(NONE, ERROR, WARN, INFO, DEBUG, FINE, FINER, FINEST)

  • 예: " user@example.com 에 대한 디버그 로그 활성화" 또는 "관리자 사용자의 최근 로그 검색"

설정

Salesforce 인증

다음 두 가지 인증 방법 중 하나를 사용하여 Salesforce에 연결할 수 있습니다.

1. 사용자 이름/비밀번호 인증(기본값)

  1. Salesforce 자격 증명 설정

  2. 보안 토큰 받기(Salesforce 설정에서 재설정)

2. OAuth 2.0 클라이언트 자격 증명 흐름

  1. Salesforce에서 연결된 앱 만들기

  2. OAuth 설정을 활성화하고 "클라이언트 자격 증명 흐름"을 선택하세요.

  3. 적절한 범위를 설정합니다(일반적으로 "api"로 충분합니다)

  4. 클라이언트 ID와 클라이언트 비밀번호를 저장하세요

  5. 중요 : 인증에 필요하므로 인스턴스 URL(예: https://your-domain.my.salesforce.com )을 기록해 두십시오.

Claude Desktop과 함께 사용

claude_desktop_config.json 에 다음을 추가하세요:

사용자 이름/비밀번호 인증의 경우:

{
  "mcpServers": {
    "salesforce": {
      "command": "npx",
      "args": ["-y", "@tsmztech/mcp-server-salesforce"],
      "env": {
        "SALESFORCE_CONNECTION_TYPE": "User_Password",
        "SALESFORCE_USERNAME": "your_username",
        "SALESFORCE_PASSWORD": "your_password",
        "SALESFORCE_TOKEN": "your_security_token",
        "SALESFORCE_INSTANCE_URL": "org_url"        // Optional. Default value: https://login.salesforce.com
      }
    }
  }
}

OAuth 2.0 클라이언트 자격 증명 흐름의 경우:

{
  "mcpServers": {
    "salesforce": {
      "command": "npx",
      "args": ["-y", "@tsmztech/mcp-server-salesforce"],
      "env": {
        "SALESFORCE_CONNECTION_TYPE": "OAuth_2.0_Client_Credentials",
        "SALESFORCE_CLIENT_ID": "your_client_id",
        "SALESFORCE_CLIENT_SECRET": "your_client_secret",
        "SALESFORCE_INSTANCE_URL": "https://your-domain.my.salesforce.com"  // REQUIRED: Must be your exact Salesforce instance URL
      }
    }
  }
}

참고 : OAuth 2.0 클라이언트 자격 증명 흐름의 경우 SALESFORCE_INSTANCE_URL 은 정확한 Salesforce 인스턴스 URL(예: https://your-domain.my.salesforce.com )이어야 합니다. 토큰 엔드포인트는 <instance_url>/services/oauth2/token 으로 생성됩니다.

사용 예

객체 검색

"Find all objects related to Accounts"
"Show me objects that handle customer service"
"What objects are available for order management?"

스키마 정보 가져오기

"What fields are available in the Account object?"
"Show me the picklist values for Case Status"
"Describe the relationship fields in Opportunity"

레코드 쿼리

"Get all Accounts created this month"
"Show me high-priority Cases with their related Contacts"
"Find all Opportunities over $100k"

사용자 정의 개체 관리

"Create a Customer Feedback object"
"Add a Rating field to the Feedback object"
"Update sharing settings for the Service Request object"

객체 간 검색

"Search for 'cloud' in Accounts and Opportunities"
"Find mentions of 'network issue' in Cases and Knowledge Articles"
"Search for customer name across all relevant objects"

Apex 코드 관리

"Show me all Apex classes with 'Controller' in the name"
"Get the full code for the AccountService class"
"Create a new Apex utility class for handling date operations"
"Update the LeadConverter class to add a new method"

Apex 트리거 관리

"List all triggers for the Account object"
"Show me the code for the ContactTrigger"
"Create a new trigger for the Opportunity object"
"Update the Case trigger to handle after delete events"

익명의 Apex 코드 실행

"Execute Apex code to calculate account metrics"
"Run a script to update related records"
"Execute a batch job to process large datasets"

디버그 로그 관리

"Enable debug logs for user@example.com"
"Retrieve recent logs for an admin user"
"Disable debug logs for a specific user"
"Configure log level to DEBUG for a user"

개발

소스에서 빌드

# Clone the repository
git clone https://github.com/tsmztech/mcp-server-salesforce.git

# Navigate to directory
cd mcp-server-salesforce

# Install dependencies
npm install

# Build the project
npm run build

기여하다

기여를 환영합니다! 풀 리퀘스트를 제출해 주세요.

특허

이 프로젝트는 MIT 라이선스에 따라 라이선스가 부여되었습니다. 자세한 내용은 라이선스 파일을 참조하세요.

문제 및 지원

문제가 발생하거나 지원이 필요한 경우 GitHub 저장소 에 문제를 제출하세요.

Available Tools

15 tools
salesforce_aggregate_queryA
Read-only

Execute SOQL queries with GROUP BY, aggregate functions, and statistical analysis. Use this tool for queries that summarize and group data rather than returning individual records.

NOTE: For regular queries without GROUP BY or aggregates, use salesforce_query_records instead.

This tool handles:

  1. GROUP BY queries (single/multiple fields, related objects, date functions)

  2. Aggregate functions: COUNT(), COUNT_DISTINCT(), SUM(), AVG(), MIN(), MAX()

  3. HAVING clauses for filtering grouped results

  4. Date/time grouping: CALENDAR_YEAR(), CALENDAR_MONTH(), CALENDAR_QUARTER(), FISCAL_YEAR(), FISCAL_QUARTER()

Examples:

  1. Count opportunities by stage:

    • objectName: "Opportunity"

    • selectFields: ["StageName", "COUNT(Id) OpportunityCount"]

    • groupByFields: ["StageName"]

  2. Analyze cases by priority and status:

    • objectName: "Case"

    • selectFields: ["Priority", "Status", "COUNT(Id) CaseCount", "AVG(Days_Open__c) AvgDaysOpen"]

    • groupByFields: ["Priority", "Status"]

  3. Count contacts by account industry:

    • objectName: "Contact"

    • selectFields: ["Account.Industry", "COUNT(Id) ContactCount"]

    • groupByFields: ["Account.Industry"]

  4. Quarterly opportunity analysis:

    • objectName: "Opportunity"

    • selectFields: ["CALENDAR_YEAR(CloseDate) Year", "CALENDAR_QUARTER(CloseDate) Quarter", "SUM(Amount) Revenue"]

    • groupByFields: ["CALENDAR_YEAR(CloseDate)", "CALENDAR_QUARTER(CloseDate)"]

  5. Find accounts with more than 10 opportunities:

    • objectName: "Opportunity"

    • selectFields: ["Account.Name", "COUNT(Id) OpportunityCount"]

    • groupByFields: ["Account.Name"]

    • havingClause: "COUNT(Id) > 10"

Important Rules:

  • All non-aggregate fields in selectFields MUST be included in groupByFields

  • Use whereClause to filter rows BEFORE grouping

  • Use havingClause to filter AFTER grouping (for aggregate conditions)

  • ORDER BY can only use fields from groupByFields or aggregate functions

  • OFFSET is not supported with GROUP BY in Salesforce

Inputs: objectName (required), selectFields (required), groupByFields (required), limit, +3 more.

salesforce_describe_objectA
Read-only

Get detailed schema metadata including all fields, relationships, and field properties of any Salesforce object. Examples: 'Account' shows all Account fields including custom fields; 'Case' shows all Case fields including relationships to Account, Contact etc.

Inputs: objectName (required).

salesforce_dml_recordsA

Perform data manipulation operations on Salesforce records:

  • insert: Create new records

  • update: Modify existing records (requires Id)

  • delete: Remove records (requires Id)

  • upsert: Insert or update based on external ID field Examples: Insert new Accounts, Update Case status, Delete old records, Upsert based on custom external ID

Inputs: records (required), operation (required), objectName (required), externalIdField.

salesforce_execute_anonymousA

Execute anonymous Apex code in Salesforce.

Examples:

  1. Execute simple Apex code: { "apexCode": "System.debug('Hello World');" }

  2. Execute Apex code with variables: { "apexCode": "List accounts = [SELECT Id, Name FROM Account LIMIT 5]; for(Account a : accounts) { System.debug(a.Name); }" }

  3. Execute Apex with debug logs: { "apexCode": "System.debug(LoggingLevel.INFO, 'Processing accounts...'); List accounts = [SELECT Id FROM Account LIMIT 10]; System.debug(LoggingLevel.INFO, 'Found ' + accounts.size() + ' accounts');", "logLevel": "DEBUG" }

Notes:

  • The apexCode parameter is required and must contain valid Apex code

  • The code is executed in an anonymous context and does not persist

  • The logLevel parameter is optional (defaults to 'DEBUG')

  • Execution results include compilation success/failure, execution success/failure, and debug logs

  • For security reasons, some operations may be restricted based on user permissions

  • This tool can be used for data operations or updates when there are no other specific tools available

  • When users request data queries or updates that aren't directly supported by other tools, this tool can be used if the operation is achievable using Apex code

Inputs: apexCode (required), logLevel.

salesforce_manage_debug_logsA

Manage debug logs for Salesforce users - enable, disable, or retrieve logs.

Examples:

  1. Enable debug logs for a user: { "operation": "enable", "username": "user@example.com", "logLevel": "DEBUG", "expirationTime": 30 }

  2. Disable debug logs for a user: { "operation": "disable", "username": "user@example.com" }

  3. Retrieve debug logs for a user: { "operation": "retrieve", "username": "user@example.com", "limit": 5 }

  4. Retrieve a specific log with full content: { "operation": "retrieve", "username": "user@example.com", "logId": "07L1g000000XXXXEAA0", "includeBody": true }

Notes:

  • The operation must be one of: 'enable', 'disable', or 'retrieve'

  • The username parameter is required for all operations

  • For 'enable' operation, logLevel is optional (defaults to 'DEBUG')

  • Log levels: NONE, ERROR, WARN, INFO, DEBUG, FINE, FINER, FINEST

  • expirationTime is optional for 'enable' operation (minutes until expiration, defaults to 30)

  • limit is optional for 'retrieve' operation (maximum number of logs to return, defaults to 10)

  • logId is optional for 'retrieve' operation (to get a specific log)

  • includeBody is optional for 'retrieve' operation (to include the full log content, defaults to false)

  • The tool validates that the specified user exists before performing operations

  • If logLevel is not specified when enabling logs, the tool will ask for clarification

Inputs: username (required), operation (required), limit, logId, +3 more.

salesforce_manage_fieldA

Create new custom fields or modify existing fields on any Salesforce object:

  • Field Types: Text, Number, Date, Lookup, Master-Detail, Picklist etc.

  • Properties: Required, Unique, External ID, Length, Scale etc.

  • Relationships: Create lookups and master-detail relationships

  • Automatically grants Field Level Security to System Administrator (or specified profiles) Examples: Add Rating__c picklist to Account, Create Account lookup on Custom Object Note: Use grantAccessTo parameter to specify profiles, defaults to System Administrator

Inputs: fieldName (required), operation (required), objectName (required), type, +14 more.

salesforce_manage_field_permissionsB

Manage Field Level Security (Field Permissions) for custom and standard fields.

  • Grant or revoke read/edit access to fields for specific profiles or permission sets

  • View current field permissions

  • Bulk update permissions for multiple profiles

Examples:

  1. Grant System Administrator access to a field

  2. Give read-only access to a field for specific profiles

  3. Check which profiles have access to a field

Inputs: fieldName (required), operation (required), objectName (required), editable, +2 more.

salesforce_manage_objectB

Create new custom objects or modify existing ones in Salesforce:

  • Create: New custom objects with fields, relationships, and settings

  • Update: Modify existing object settings, labels, sharing model Examples: Create Customer_Feedback__c object, Update object sharing settings Note: Changes affect metadata and require proper permissions

Inputs: operation (required), objectName (required), label, description, +5 more.

salesforce_query_recordsA
Read-only

Query records from any Salesforce object using SOQL, including relationship queries.

NOTE: For queries with GROUP BY, aggregate functions (COUNT, SUM, AVG, etc.), or HAVING clauses, use salesforce_aggregate_query instead.

Examples:

  1. Parent-to-child query (e.g., Account with Contacts):

    • objectName: "Account"

    • fields: ["Name", "(SELECT Id, FirstName, LastName FROM Contacts)"]

  2. Child-to-parent query (e.g., Contact with Account details):

    • objectName: "Contact"

    • fields: ["FirstName", "LastName", "Account.Name", "Account.Industry"]

  3. Multiple level query (e.g., Contact -> Account -> Owner):

    • objectName: "Contact"

    • fields: ["Name", "Account.Name", "Account.Owner.Name"]

  4. Related object filtering:

    • objectName: "Contact"

    • fields: ["Name", "Account.Name"]

    • whereClause: "Account.Industry = 'Technology'"

Note: When using relationship fields:

  • Use dot notation for parent relationships (e.g., "Account.Name")

  • Use subqueries in parentheses for child relationships (e.g., "(SELECT Id FROM Contacts)")

  • Custom relationship fields end in "__r" (e.g., "CustomObject__r.Name")

Inputs: fields (required), objectName (required), limit, orderBy, +1 more.

salesforce_read_apexA
Read-only

Read Apex classes from Salesforce.

Examples:

  1. Read a specific Apex class by name: { "className": "AccountController" }

  2. List all Apex classes with an optional name pattern: { "namePattern": "Controller" }

  3. Get metadata about Apex classes: { "includeMetadata": true, "namePattern": "Trigger" }

  4. Use wildcards in name patterns: { "namePattern": "AccountCont" }

Notes:

  • When className is provided, the full body of that specific class is returned

  • When namePattern is provided, all matching class names are returned (without body)

  • Use includeMetadata to get additional information like API version, length, and last modified date

  • If neither className nor namePattern is provided, all Apex class names will be listed

  • Wildcards are supported in namePattern: * (matches any characters) and ? (matches a single character)

Inputs: className, namePattern, includeMetadata.

salesforce_read_apex_triggerA
Read-only

Read Apex triggers from Salesforce.

Examples:

  1. Read a specific Apex trigger by name: { "triggerName": "AccountTrigger" }

  2. List all Apex triggers with an optional name pattern: { "namePattern": "Account" }

  3. Get metadata about Apex triggers: { "includeMetadata": true, "namePattern": "Contact" }

  4. Use wildcards in name patterns: { "namePattern": "Account*" }

Notes:

  • When triggerName is provided, the full body of that specific trigger is returned

  • When namePattern is provided, all matching trigger names are returned (without body)

  • Use includeMetadata to get additional information like API version, object type, and last modified date

  • If neither triggerName nor namePattern is provided, all Apex trigger names will be listed

  • Wildcards are supported in namePattern: * (matches any characters) and ? (matches a single character)

Inputs: namePattern, triggerName, includeMetadata.

salesforce_search_allA
Read-only

Search across multiple Salesforce objects using SOSL (Salesforce Object Search Language).

Examples:

  1. Basic search across all objects: { "searchTerm": "John", "objects": [ { "name": "Account", "fields": ["Name"], "limit": 10 }, { "name": "Contact", "fields": ["FirstName", "LastName", "Email"] } ] }

  2. Advanced search with filters: { "searchTerm": "Cloud*", "searchIn": "NAME FIELDS", "objects": [ { "name": "Account", "fields": ["Name", "Industry"], "orderBy": "Name DESC", "where": "Industry = 'Technology'" } ], "withClauses": [ { "type": "NETWORK", "value": "ALL NETWORKS" }, { "type": "SNIPPET", "fields": ["Description"] } ] }

Notes:

  • Use * and ? for wildcards in search terms

  • Each object can have its own WHERE, ORDER BY, and LIMIT clauses

  • Support for WITH clauses: DATA CATEGORY, DIVISION, METADATA, NETWORK, PRICEBOOKID, SNIPPET, SECURITY_ENFORCED

  • "updateable" and "viewable" options control record access filtering

Inputs: objects (required), searchTerm (required), searchIn, viewable, +2 more.

salesforce_search_objectsA
Read-only

Search for Salesforce standard and custom objects by name pattern. Examples: 'Account' will find Account, AccountHistory; 'Order' will find WorkOrder, ServiceOrder__c etc.

Inputs: searchPattern (required).

salesforce_write_apexA

Create or update Apex classes in Salesforce.

Examples:

  1. Create a new Apex class: { "operation": "create", "className": "AccountService", "apiVersion": "58.0", "body": "public class AccountService { public static void updateAccounts() { /* implementation */ } }" }

  2. Update an existing Apex class: { "operation": "update", "className": "AccountService", "body": "public class AccountService { public static void updateAccounts() { /* updated implementation */ } }" }

Notes:

  • The operation must be either 'create' or 'update'

  • For 'create' operations, className and body are required

  • For 'update' operations, className and body are required

  • apiVersion is optional for 'create' (defaults to the latest version)

  • The body must be valid Apex code

  • The className in the body must match the className parameter

  • Status information is returned after successful operations

Inputs: body (required), className (required), operation (required), apiVersion.

salesforce_write_apex_triggerA

Create or update Apex triggers in Salesforce.

Examples:

  1. Create a new Apex trigger: { "operation": "create", "triggerName": "AccountTrigger", "objectName": "Account", "apiVersion": "58.0", "body": "trigger AccountTrigger on Account (before insert, before update) { /* implementation */ }" }

  2. Update an existing Apex trigger: { "operation": "update", "triggerName": "AccountTrigger", "body": "trigger AccountTrigger on Account (before insert, before update, after update) { /* updated implementation */ }" }

Notes:

  • The operation must be either 'create' or 'update'

  • For 'create' operations, triggerName, objectName, and body are required

  • For 'update' operations, triggerName and body are required

  • apiVersion is optional for 'create' (defaults to the latest version)

  • The body must be valid Apex trigger code

  • The triggerName in the body must match the triggerName parameter

  • The objectName in the body must match the objectName parameter (for 'create')

  • Status information is returned after successful operations

Inputs: body (required), operation (required), triggerName (required), apiVersion, +1 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.2/5.0

    Scored across 15 tools

    Disambiguation5/5

    Each tool targets a clearly distinct resource/action pair. Query vs. aggregate query are explicitly disambiguated via cross-references; search objects (metadata) vs. search all (records) are differentiated; Apex class and trigger tools are separate. No genuine overlap.

    Naming Consistency5/5

    All tools consistently use the 'salesforce_' prefix followed by snake_case names with verb-like prefixes (describe, query, search, manage, read, write, execute). Minor deviations like 'aggregate_query' and 'execute_anonymous' still fit the overall predictable pattern.

    Tool Count5/5

    15 tools is at the upper end of the ideal range, but each tool earns its place by covering distinct Salesforce workflows: data querying, DML, metadata management, Apex code, and debug logs. No redundancy or bloat.

    Completeness4/5

    The tool set provides solid lifecycle coverage: record CRUD via dml_records, query and aggregate query, SOSL search, object/field metadata management, Apex class/trigger read/write, and anonymous execution. The main gap is lack of explicit delete operations for metadata (objects, fields, Apex classes/triggers), but execute_anonymous can act as a workaround in some cases.

    Maintenance

    ActivitySlowing
    ResponsivenessLimited data

    Related MCP Connectors

    Related MCP Servers