Give your agent the architecture, not a pile of files

Endpoint

POST https://<your-server>/api/v1/mcp, JSON-RPC 2.0 over HTTP (request–response)

Authentication

Authorization: Bearer ink_…, a personal API key, scoped and revocable

Hosting

Self-hosted. Part of the Inwardis server you run with Docker; your model never leaves it.

Tools

The server exposes 55 tools on a default install, listed below.

What an agent does with it

• Reads before it writes code. One call gives the top level of a model; the agent descends only where the task needs it, instead of reading a folder of documents end to end.
• Answers "what depends on this?" Relations and cross-project references are followed in both directions, so impact is a query, not a guess.
• Builds and corrects the model. Create projects, elements and relations in one atomic batch, move and retype them, curate views and lay them out.
• Checks its own picture. render_view returns the diagram as SVG with a summary of what it actually drew, so an agent can see a clipped label or a missing line.
• Leaves a trail people can read. Every change appears in the activity feed under the key's name, the agent can leave a short note on what it did, and comments go both ways.

Connect your agent

1. Run Inwardis (download, or start a 30-day trial).
2. In the app, open the user menu → API Keys… and create a key. The dialog shows the ready-made command with your server's address filled in.
3. Add the server to your client with one of the snippets below. Use one key per client, so one can be revoked without breaking the other.

Claude Code

claude mcp add --transport http inwardis https://<your-server>/api/v1/mcp \
  --header "Authorization: Bearer ink_…"

Cursor (.cursor/mcp.json)

{
  "mcpServers": {
    "inwardis": {
      "url": "https://<your-server>/api/v1/mcp",
      "headers": { "Authorization": "Bearer ink_…" }
    }
  }
}

VS Code (.vscode/mcp.json)

{
  "servers": {
    "inwardis": {
      "type": "http",
      "url": "https://<your-server>/api/v1/mcp",
      "headers": { "Authorization": "Bearer ink_…" }
    }
  }
}

Any other client that speaks MCP over HTTP with a custom header works the same way. Start the session by calling learn: the server teaches the agent how the model is organised and how to read it level by level. The Inwardis VS Code extension is separate from the MCP server: it mounts the model as folders and files for you, and ships with the product.

The tools

Grouped by what they are for. Your client shows each tool's full description after connecting.

What the key can and cannot do

• It acts as you. A key sees exactly the projects its owner can see, and can do nothing its owner's login cannot.
• It is scoped and revocable. Read, write and action scopes are separate; an administrator sees and can revoke every key.
• It is rate-limited. Per key, with limits the operator sets.
• Nothing leaves your server. The MCP server is part of your installation. Which agent you connect, and where it runs, is your decision.
• It can be switched off. A fresh installation has no keys, so the endpoint grants nothing until someone creates one; an administrator can also turn the endpoint off entirely.