What is an MCP server?
An MCP server is a named, hosted process that exposes one or more tools to any MCP-compatible AI client. When the AI connects to your server, it discovers all available tools and their input schemas — then decides which ones to call based on the conversation. Each server gets its own:- Subdomain URL —
https://your-subdomain.mcpcore.io/mcp(chosen by you at creation time) - Security mode — independent auth configuration (Public, Unlisted, API Key, or OAuth)
- Tool collection — the functions the AI can call
- Environment secrets — encrypted key-value pairs referenced as
env.KEY_NAME
| Pattern | Example subdomain |
|---|---|
| One server per project | github-tools, jira-tools, slack-bot |
| One server per environment | my-api-dev, my-api-prod |
| One server per team | data-team, infra-tools |
| One server per customer | acme-corp, example-inc |
Create a server
Navigate to My Servers
From the dashboard sidebar, click My Servers, then click the New Server button.
Fill in the server details
The creation form has the following fields:
Code
A unique machine identifier for your server (5–100 characters). Used internally and in integration configs. Must be insnake_case or camelCase format.Example:github_tools,slackBot,inventory_api
Title
A human-readable name displayed in the dashboard (5–255 characters).Example:GitHub Tools,Slack Bot,Inventory API
Description (optional)
A short description of what this server does (max 255 characters).Category
Select the category that best describes your server’s purpose:| Category | Use for |
|---|---|
| Data & Database | Database connections, SQL, NoSQL, data warehouses |
| Files & Documents | File systems, cloud storage, document management |
| Web & Search | Web scraping, search engines, external APIs |
| DevTools & Repositories | Git, version control, CI/CD, code hosting |
| Messaging & Collaboration | Slack, Teams, email, communication platforms |
| Business & Productivity | CRM, ERP, project management, analytics |
| AI & ML Services | Machine learning APIs, AI models, NLP services |
| Automation & Workflows | Zapier, workflow engines, task automation |
| Security & Auth | Authentication, authorization, security tools |
| Custom & Internal | Internal tools, custom integrations |
| Other | Uncategorized or specialized services |
Subdomain
The subdomain for your server’s endpoint (1–63 characters). Must contain only lowercase letters, numbers, and hyphens; cannot start or end with a hyphen.Your server will be reachable athttps://your-subdomain.mcpcore.io/mcp. Choose something short and memorable.Example:github-tools→https://github-tools.mcpcore.io/mcp
Instructions (optional)
Custom system-level instructions sent to the AI when it connects to this server. Use this to give the AI context about your tools’ intended scope, tone, or constraints.
Example: Only use these tools for read-only operations. Never modify data unless explicitly asked.
Transport Type
Currently only Streamable is available — the default real-time streaming transport for MCP.Rate Limit Per Minute
Maximum number of tool calls per minute (0 = unlimited, max 5000). Use this to protect backend services from excessive AI-driven calls.Default: 60 requests/minute
Security Mode
How incoming requests are authenticated. See Security Overview for a full comparison.The server detail page
Once created, the server detail page is your central hub:
| Tab | What’s here |
|---|---|
| Overview | Subdomain URL, security info, tools list, environment secrets, recent logs and traffic |
| Analytics | Request volume, error rate, latency, tool breakdown, session and hourly trends |
| Integration | Ready-to-paste config snippets for Claude Desktop, Cursor, VS Code, Windsurf, and Cline |