@fias/mcp-server

Connect external AI agents (Claude Code, or any MCP client) to your Fias arches — contacts, calendar, todo lists, email, leads, and more — through the Model Context Protocol.

This is a thin stdio transport over the Fias Agent Tools API. All enforcement — authentication, scopes, which tools exist, billing, audit — happens server-side; the package itself grants nothing.

Setup

1. Create a Fias API key (Fias account → API keys) with scope:

   • agent-tools:read — search/read tools (emails, contacts, events, documents, …)
   • agent-tools:write — optionally, in-product write tools (create a todo, draft an email, update a contact, …)
   • An administrative access scope — optionally, and only if your roles authorize one. These appear as their own checkboxes on the key form; tick one to add the matching platform-authoring tools (see Admin tools below). A key carrying one cannot also be bound to a workspace, so if you need both, create two keys.

2. Add to Claude Code:

   claude mcp add fias -e FIAS_API_KEY=fias_sk_... -- npx -y @fias/mcp-server

   Or configure any MCP client with command npx -y @fias/mcp-server and the FIAS_API_KEY environment variable. Set FIAS_API_URL to point at a non-production environment, and FIAS_REQUEST_TIMEOUT_MS (default 60000) to change how long a single call may hang before it gives up. Calls are independent: a slow or stalled request fails only itself, and your client's cancellation aborts it immediately.

3. Ask your agent things like "mark the deploy task complete in my Fias todo list" or "what unanswered emails do I have?".

What agents can and cannot do

• Read tools are available to every agent key.
• Write tools (create/update inside your Fias workspace) require the agent-tools:write scope — an explicit choice you make per key.
• Outward actions — sending email, publishing posts, anything a third party can observe — are never available to external agents. Those require your explicit per-action approval in the Fias app; the agent will tell you when that's the case.
• Admin tools (platform content authoring) appear only on keys carrying a dedicated admin scope, which only a user whose roles authorize it can mint — and the owner's role is re-checked on every call, so losing the role stops those tools on the agent's next request. Write-tier admin tools also need agent-tools:write: with the admin scope alone the key can read the catalog but not change it. If you hold the role and the tools still don't appear, check the key's scopes first — the tools are absent from tools/list entirely rather than failing when called.

Revoke a key at any time in Fias account → API keys; agents lose access immediately.