What is a Server?
An MCP server in GetMCP is a named container that groups related tools, resources, and prompts together. Each server gets a unique public URL that AI clients connect to via the MCP protocol.
Think of a server as a “workspace” for a specific domain or purpose:
- A Stripe server with tools for payments, customers, and subscriptions
- A GitHub server with tools for repos, issues, and pull requests
- An Internal CRM server with tools for your company’s custom CRM API
Server URL Structure
Each server gets a unique endpoint URL:
https://yoursite.com/mcp/{slug}/{server_id}
- slug — A human-readable identifier derived from the server name (e.g.,
my-stripe-tools)
- server_id — A 16-character hex token for URL security (e.g.,
a1b2c3d4e5f6a1b2)
The server_id is optional in the URL — the server will respond without it — but including it adds a layer of security by making the URL unguessable.
Server Properties
| Property | Description |
|---|
| Name | Human-readable label displayed in the admin and sent to AI clients |
| Slug | URL path segment; auto-generated from name, must be unique |
| Status | active, paused, or draft |
| Auth Type | Inbound authentication method for protecting the MCP endpoint |
| Transport | Always streamable-http (JSON-RPC 2.0 over HTTP) |
| Rate Limit | Maximum requests per minute (default: 60) |
| CORS Origins | Comma-separated list of allowed origins for browser clients |
Server Status
| Status | Description |
|---|
active | Accepting MCP connections; tools are callable |
paused | Returns HTTP 503 to AI clients; configuration preserved |
draft | Not yet published; not accessible via MCP endpoint |
Inbound Authentication
You can protect your MCP endpoint so only authorized AI clients can connect:
| Auth Type | Description |
|---|
none | No authentication required (suitable for testing) |
api-key | Clients must send an API key in the Authorization header |
oauth | OAuth 2.0 client credentials flow |
For production deployments, always use an authentication method. Anyone with the server URL can call your tools and consume API credits if authentication is disabled.
Test Credentials
Servers support separate test credentials — a second set of outbound API keys used when running tool tests from the admin interface. This lets you verify tool configurations against a test/staging API environment without touching production keys.
Creating a Server
Open the Dashboard
Navigate to GetMCP > Dashboard in WordPress admin.
Click Create Server
Click the Create Server button.
Fill in Details
Enter a name and optional description. The slug and server ID are auto-generated.
Configure Authentication
Optionally set an inbound auth type and CORS origins if needed.
Save
Click Create. The server is now active and accessible.
Multi-Server Architecture
You can create as many servers as you need from a single WordPress installation. This lets you:
- Organize by domain: separate servers for different APIs or clients
- Segment by access level: different API keys for different servers
- Isolate environments: separate staging and production server configs
