Local MCP server
The Model Context Protocol (MCP) lets local coding agents use Authsia without receiving your secrets. Connect Codex, Claude Code, Cursor, Devin Desktop, or VS Code; the client manages the local server while Authsia keeps its existing approvals, Keychain access, audit, and masking.
MCP integrations are off by default. Enable MCP Integrations in Settings > Developer Access before connecting a client. Client configuration cannot enable this app-level control.
MCP setup and launch commands (configure, wrap, unwrap, declare, catalog, serve, proxy, start, and restart) fail while MCP Integrations is off. Enable MCP Integrations in Authsia Settings > Developer Access, then retry. The CLI never changes the toggle. Help, status, doctor, activity export, stop, and portal revocation remain available for inspection and cleanup.
Use a user-global client entry
Print the user-global fallback for the exact installed Authsia binary, then add the printed entries in your client’s MCP settings. From a managed workspace, declared upstreams appear as separate proxy entries; otherwise the output stays serve-only. The read-only report groups existing user-global and project entries by workspace and labels the exact path, scope, and effective, overridden, or conditional precedence. Project-scoped Claude, Cursor, and VS Code entries outrank matching user-global entries, and declarations never cross repository roots. Replace vscode with codex, claude, cursor, or devin as needed. The command never embeds credentials or fixes a repository path.
Let the MCP client launch Authsia
Your MCP client starts authsia mcp serve itself. Authsia checks its app-level MCP setting on every tool call and fails closed while disabled. Do not start it from an agent terminal; use the client’s MCP controls if the tools are missing or disconnected.
Gate a third-party MCP
To wrap, catalog, or proxy a workspace-declared stdio upstream, or to protect localhost Streamable HTTP, see MCP Manager.
Six fixed tools
Fixed tools
authsia_status, authsia_workspace_inspect, authsia_list, authsia_exec, authsia_access_status, and authsia_access_revoke.
One workspace at a time
One global client entry works across initialized Authsia workspaces. Workspace tools use the active repository and remain unavailable until one is selected.
No secret-return tool
MCP can inspect safe workspace state, list scoped metadata, and run approved commands. Empty item categories return an empty page, not an operation failure. MCP cannot read or return plaintext secrets, global audit history, or Vault administration data.
Approval remains independent
For metadata listing and credential-dependent execution, Authsia uses the same scoped Agent JIT approval on your Mac or paired iPhone. Client-side tool approval is only a convenience; it never grants secret access. Grant status and revocation are limited to the current MCP server instance.
After adding the entry, reload or restart the client and confirm that authsia_status appears in its tool picker before starting an agent task.