Skip to content

docs: Add MCP server naming constraints #1268

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from
Open

docs: Add MCP server naming constraints #1268

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions docs/integrations/mcp-servers.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -57,6 +57,18 @@ MCP servers are configured per repository using a JSON configuration file. The c
- **Access controls** - Specify permissions and security settings
- **Environment variables** - Configure server-specific settings and secrets

### Server Naming Requirements

MCP server names must follow strict naming conventions to ensure compatibility:

- **Allowed characters**: Only alphanumeric characters (a-z, A-Z, 0-9), hyphens (-), and underscores (_)
- **Length limit**: Maximum 128 characters
- **Pattern**: Must match the regex `^[a-zA-Z0-9_-]{1,128}$`

<Warning>
Server names containing dots (.), spaces, or other special characters will cause connection failures. For example, `awslabs.aws-documentation-mcp-server` should be renamed to `awslabs-aws-documentation-mcp-server`.
</Warning>

## Permissions

The Codegen MCP integration requires the following permissions:
Expand Down