Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.archyon.app/llms.txt

Use this file to discover all available pages before exploring further.

Archyon ships a hosted Model Context Protocol server at https://archyon.app/mcp. Once connected, Claude can read and modify your workspaces, components, relationships, processes, people, teams, and stakeholder roles directly — no manual data export, no copy-paste between tools. This is the recommended install for any production use. The legacy local subprocess install is documented at the bottom of this page for self-hosted deployments and local development.

​
Add Archyon to Claude

​
claude.ai (browser)

  1. Open the Connectors settings: Settings → Connectors → Add custom connector.
  2. Paste the MCP URL: 
    https://archyon.app/mcp
  3. Click Connect. A browser window opens at archyon.app for sign-in (or jumps straight to the consent screen if you’re already signed in).
  4. Select which Archyon organization the connection should act in. The binding is permanent — to change organizations later, remove and re-add the connector.
  5. Click Allow.
The connector is now available in any conversation. Claude can list workspaces, read full architectures, create components, write processes, and manage stakeholders in the bound organization.

​
Claude Code (CLI)

claude mcp add --transport=http archyon https://archyon.app/mcp
The CLI opens a browser window for the OAuth flow. Same consent screen as the web app — pick your organization, click Allow, return to the terminal. Verify the connection: 
claude mcp list
archyon should appear in the list with a connected status.

​
How authorization works

Connections use standard OAuth 2.1 with PKCE. Archyon does not see your Claude credentials and Claude does not see your Archyon password.
  1. Claude opens https://archyon.app/oauth/authorize in your browser.
  2. You sign in to Archyon (or the existing session is reused).
  3. The consent screen shows the requesting client name, your identity, and the Archyon organization that will be bound. You select the organization and approve.
  4. Archyon issues a short-lived access token plus a long-lived refresh token, both scoped to the chosen organization.
  5. Claude stores both tokens locally and uses them on every tool call. The access token rotates roughly every hour via the refresh token; you don’t see this.
The access tokens never leave Claude’s local storage. You can revoke a connection at any time from Account → Connectors in Archyon; revocation invalidates both tokens immediately.

​
What the connector can do

Once connected, Claude can call any of the following groups of tools:
ToolsOperations
WorkspacesList, get (with full contents), create, delete
ComponentsCreate, update, delete, plus list/add/remove external links
RelationshipsCreate, update, delete
StakeholdersList on a component, add (person or team), remove
ProcessesList, get, create from Mermaid source, update, delete
PeopleList, get (with team memberships), create, update, delete
TeamsList, get (with members), create, update, delete; add/update/remove members
Stakeholder rolesList, create custom roles, update, delete
NotionSearch the connected Notion workspace from inside Claude
SchemaList built-in component / relationship / lifecycle types
A complete tool reference is published as part of the MCP server itself — once connected, Claude will surface tool descriptions automatically during conversations.

​
Switching organizations

A connector is bound to one Archyon organization at consent time. If you need Claude to act in a different organization:
  1. In Archyon, switch organizations using the header switcher.
  2. Either:
    • Remove the existing connector in Claude and re-add it (cleanest), or
    • Add a second connector with a distinct name. Archyon supports multiple simultaneous connections per user, each bound to a different organization.

​
Managing connectors

Account → Connectors in the Archyon application lists every active connection by client name, target organization, and last-used timestamp. Use the Revoke action there to invalidate a connection’s tokens immediately.

​
Self-hosted instances

A self-hosted Archyon deployment exposes the same MCP endpoint at <your-base-url>/mcp. Use that URL in place of https://archyon.app/mcp when adding the connector. The same OAuth flow applies; ensure PUBLIC_BASE_URL is set correctly in your deployment environment so the discovery metadata returns the right hostname.

​
Legacy: local stdio server

A local subprocess MCP server lives in mcp-server/ in the repository. It uses the stdio transport and authenticates with a Personal Access Token. This install path predates the hosted MCP and is kept primarily for self-hosted dev environments. Hosted MCP supersedes this for production. Prefer the hosted install unless you have a specific reason to run a subprocess.