Skip to main content

​
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)
  • Custom domain — optionally use your own domain with automatic SSL
  • 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
You can create as many servers as you need. Common patterns:

​
Create a server

1

Navigate to My Servers

From the dashboard sidebar, click My Servers, then click the New Server button.
2

Fill in the server details

The creation form has the following fields:

​
Code

A unique machine identifier for your server (max 20 characters). Used internally and in integration configs. Must be in snake_case or camelCase format.
Example: github_tools, slackBot

​
Title

A human-readable name displayed in the dashboard (max 100 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:

​
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 at https://your-subdomain.mcpcore.io/mcp. Choose something short and memorable.
Example: github-tools → https://github-tools.mcpcore.io/mcp
Subdomains must be globally unique across all MCPCore accounts. If your preferred subdomain is taken, try adding a suffix (e.g. my-github-tools).

​
Custom Domain (optional)

You can use your own domain instead of the default mcpcore.io subdomain. Enter your domain (e.g. mcp.yourcompany.com) and point a CNAME record to your MCPCore subdomain. SSL is provisioned automatically.
Custom domains are available on paid plans. MCPCore monitors SSL certificate status and performs periodic verification.

​
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.
3

Click Create server

Your server is live immediately. You’ll be redirected to the server detail page where you can start adding tools.

​
The server detail page

Once created, the server detail page is your central hub. The page is organised into tabs:

​
Your server’s endpoint URL

Your server’s MCP endpoint URL is based on the subdomain you chose:
If you configured a custom domain:
For Unlisted mode, the URL includes an embedded secret key:
Copy the endpoint URL from the Overview section of the server detail page. This URL is permanent — it never changes if you rename the server or update its settings.

​
Next steps

Configure security

Choose and configure the right security mode for your use case.

Add tools

Write the JavaScript tool functions this server will expose.