C4 architecture model of your system, built from code by your AI and read back as focused context.
Connect Remote server
claude mcp add --transport http keystone https://keystone-core.pro/mcp --header "Authorization: Bearer <YOUR_API_KEY>"
{
"mcpServers": {
"keystone": {
"url": "https://keystone-core.pro/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}
{
"servers": {
"keystone": {
"type": "http",
"url": "https://keystone-core.pro/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}
Settings > Connectors > Add custom connector
URL: https://keystone-core.pro/mcp
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server asks for a key before it lists its tools. Connect it with your own key to see them.
Headers
| Name | Description |
|---|---|
AuthorizationRequired, secret | Bearer <Keystone AI token>: create one in a project, AI assistant → Connection → Create token |
Details
| Endpoint | https://keystone-core.pro/mcp (Streamable HTTP) |
| First published | 10 Nov 2026 |
| Last updated | 10 Nov 2026 |
| Registry name | pro.keystone-core/keystone |
More developer tools servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
