MCP setup

Connect your agent to Core Edge.

Core Edge is CLI-first, but agents that cannot use a shell can still access a Core namespace through hosted or local MCP.

Endpoint

https://core-edge.slayteksystems.com/mcp

Connect your host

Signing in does not create an account. You need an admitted account for The Core. A verified date appears only where a dated host receipt exists.

HostStepsSign-inVerified
Claude Code
  1. Run claude mcp add --transport http core https://core-edge.slayteksystems.com/mcp.
  2. Run /mcp in Claude Code, choose core and sign in.
OAuth sign-in. Its callback is admitted on this server.Not yet verified
claude.ai and Claude desktop
  1. Open Customize > Connectors, choose + Add, then Add custom connector.
  2. Name it The Core and enter https://core-edge.slayteksystems.com/mcp.
  3. Keep OAuth sign-in, choose Add, then Connect and sign in.
OAuth sign-in. Its callback is admitted on this server.Not yet verified
Codex
  1. Run codex mcp add core --url https://core-edge.slayteksystems.com/mcp.
  2. Run codex mcp login core and sign in.
OAuth sign-in. Its callback is admitted on this server.Not yet verified
ChatGPT
  1. Open Plugins, choose +, then Add custom MCP server.
  2. Name it The Core and enter https://core-edge.slayteksystems.com/mcp as the connection URL.
  3. Choose OAuth, accept the warning, choose Create as a plugin and sign in.
  4. Workspace policy decides whether custom MCP servers are allowed on your plan.
OAuth sign-in. Its callback is admitted on this server.Not yet verified
Cursor

Add to Cursor

  1. Open the Add to Cursor link and confirm the install.
  2. Sign in when Cursor shows the server as needing authentication.
OAuth sign-in. Its callback is admitted on this server.Not yet verified
VS Code

Add to VS Code

  1. Open the Add to VS Code link, review the server and choose Install.
  2. Start the server and sign in when VS Code asks.
OAuth sign-in is not available yet. This server does not admit the vscode.dev and insiders.vscode.dev callback, so registration fails. An unattended setup can send a machine key as a bearer header instead.Not yet verified
Windsurf
  1. Open ~/.codeium/windsurf/mcp_config.json.
  2. Add "core": {"serverUrl": "https://core-edge.slayteksystems.com/mcp"} under mcpServers.
  3. Refresh MCP servers in Cascade and sign in.
Not confirmed. The Core has not checked this host's sign-in callback or header support.Not yet verified
Gemini CLI
  1. Run gemini mcp add --transport http core https://core-edge.slayteksystems.com/mcp.
  2. Run /mcp auth core in Gemini CLI and sign in.
OAuth sign-in. Its callback is admitted on this server.Not yet verified
JetBrains AI Assistant
  1. Open Settings > Tools > AI Assistant > Model Context Protocol (MCP) and choose Add.
  2. Enter {"mcpServers": {"core": {"url": "https://core-edge.slayteksystems.com/mcp"}}}.
Not confirmed. The Core has not checked this host's sign-in callback or header support.Not yet verified

Choose a connection path

Client capabilityUse this pathAuthentication
Can run terminal commands Use the core-edge CLI. After installation, core-edge skill --install can install the matching local skill. Humans install the Core Edge CLI, run core-edge login and finish the browser or device sign-in. Human credentials stay in the operating system's credential store. Do not use a machine key with core-edge login.
Can call hosted Streamable HTTP MCP with bearer auth Point the client at the hosted /mcp endpoint. Configure Authorization: Bearer <machine-key> or the bearer-token field your client provides, from the client's secret settings.
Supports OAuth/Mixed Auth for remote MCP Add the MCP URL. The client discovers sign-in through its metadata document, or Dynamic Client Registration when offered. Sign in to The Core and choose the spaces to grant. No key is needed.

Learn the operating model

Connection is only the first step. Read the complete agent operating guide for spaces, search-before-write, typed records, links, the first useful shared context, and second-agent continuity.

Create a machine key

An unattended agent uses its own read or write machine key. An account admin creates it on the Agent keys page at https://core-edge.slayteksystems.com/app/agent-keys. Inject it through the agent's secret environment as CORE_AUTH_TOKEN and set CORE_AGENT_NAME. An MCP client without OAuth sends the same key as a bearer token from its secret settings. Machine keys are never admin, owner or namespace-admin credentials. Never put a key in chat, source control, a shell profile or a command argument.

Admins can also create one from the CLI. The mcp purpose label is provenance only; role and space grants are the access boundary.

core-edge keys create my-agent --role write --purpose mcp

Use read instead of write for read-only connectors.

OAuth clients

For remote hosted clients that support OAuth or Mixed Auth, use these values:

Discovery endpoints:

Hosted MCP clients connect to https://core-edge.slayteksystems.com/mcp. When the client supports OAuth, a human signs in to The Core in the client's sign-in window and chooses which spaces the client may read or write. No key is entered on the sign-in page. Installing a plugin or adding the URL does not create an account or grant access.

Security boundary

MCP receives the same space-scoped access as the machine key or the spaces approved at sign-in. Key management, hard delete, approval review, migrations, raw arbitrary API requests, and operator controls are not exposed through the default MCP tool surface.