MCP Server

Pro Available on the Pro tier.

The Inklings MCP server exposes your workspace as a set of tools and resources that any MCP-compatible AI client can use — Claude Code, Cursor, or any other tool that speaks the Model Context Protocol. The server runs inside the Inklings app, bound to localhost, and requires bearer token authentication. Nothing leaves your machine except what your MCP client explicitly requests.

Enable the MCP server

1. Open Settings from the sidebar.
2. Navigate to the MCP Server section.
3. Toggle Enable MCP Server on.

The server starts immediately. The settings panel updates to show:

• The server URL (e.g., http://127.0.0.1:7862/mcp)
• A status indicator confirming the server is running

The server stops when you close or switch away from the workspace, and restarts automatically when you reopen the workspace with MCP enabled in settings.

Workspace required

The MCP server requires an open workspace. Enabling MCP in settings while no workspace is open saves the preference but does not start the server until a workspace is opened.

Get your bearer token

The server protects all endpoints with bearer token authentication. To retrieve your token:

1. Open Settings → MCP Server.
2. Click Show Token (or the equivalent reveal control).

The token is a 64-character hex string generated from a cryptographically secure random source. Copy it and configure it in your MCP client.

The status response from the server never includes the token value — you must retrieve it explicitly from settings. This prevents token leakage during routine status polling.

Regenerate the token

If you need to invalidate a token (for example, after sharing it accidentally):

1. Open Settings → MCP Server.
2. Click Regenerate Token.

The server restarts with a new token. The old token immediately stops working for all authenticated requests. Update your MCP client configuration with the new token.

Configure your MCP client

Add Inklings to your MCP client’s server list with these values:

Setting	Value
Transport	Streamable HTTP
URL	http://127.0.0.1:7862/mcp (or your configured port)
Authorization	Bearer <your-token>

For Claude Code, add a .claude/mcp.json entry or use the claude mcp add command per Claude Code’s documentation.

Change the port

The default port is 7862. To use a different port:

1. Open Settings → MCP Server.
2. Update the Port field.
3. Re-enable the server if it was running.

Ports below 1024 are rejected — the server will not bind to privileged ports. Valid range: 1024–65535.

Health check

The /health endpoint is unauthenticated and returns a JSON readiness status:

GET http://127.0.0.1:7862/health

Response:

{"status": "ok", "version": "x.y.z"}

Use this endpoint to verify the server is running before sending authenticated requests.

Authentication details

All requests to /mcp require the Authorization: Bearer <token> header. Requests without this header — or with an incorrect token — receive HTTP 401. The server uses constant-time comparison to prevent timing-based token guessing.

The /health endpoint is the only path accessible without a token.

What the MCP server exposes

The server exposes workspace tools and resources. See the MCP Tools Catalog for the full list.

See Also

• MCP Tools Catalog — All tools and resources exposed via MCP
• Getting Started with Agent — The built-in agent (separate from MCP)
• Settings Reference — Full settings reference including MCP configuration