AI agents & MCP

Snapi's Model Context Protocol (MCP) server is live at https://api.snapi.ca/mcp. Any MCP-compatible AI assistant — Claude, Cursor, Windsurf, n8n agents, and others — can read and write your workspace through natural language: forms, records, kanban boards, comments, and file attachments.

What is MCP?

The Model Context Protocol is an open standard that lets AI assistants call tools on external systems. Instead of building prompt engineering hacks, you configure an MCP server once and the AI gets structured, reliable access to your data.

Snapi's MCP server exposes your forms, records, and boards as tools the AI can invoke. The assistant can answer questions like "How many leads came in this week?" or "Move record X to the Approved column" without you writing a single line of code.

Connecting

The server speaks MCP's Streamable HTTP transport at https://api.snapi.ca/mcp and authenticates with a Snapi API key sent as a header — either Authorization: Bearer snapi_... or X-API-Key: snapi_.... Get a key from Settings → API Keys and give it an access level: what the key may do is what the agent may do.

Claude Code (CLI)

claude mcp add --transport http snapi https://api.snapi.ca/mcp \
  --header "Authorization: Bearer snapi_your_key_here"

Claude Desktop

Claude Desktop connects to remote servers through a local bridge. Add to claude_desktop_config.json:

{
  "mcpServers": {
    "snapi": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote", "https://api.snapi.ca/mcp",
        "--header", "Authorization: Bearer snapi_your_key_here"
      ]
    }
  }
}

Other MCP hosts (Cursor, Windsurf, n8n, custom)

Any host that supports HTTP-based MCP servers just needs the URL and the auth header:

URL:    https://api.snapi.ca/mcp
Header: Authorization: Bearer snapi_your_key_here
i
Access levels. The key's level caps the agent: Viewer = read-only, Editor = create/update records, move cards, comment, attach files, Admin = editor plus create/edit/delete forms and boards. Use the whoami tool to see the effective level. See API keys.

Available MCP tools

Connected assistants get 33 tools. The agent discovers them automatically — this list is for planning which access level a task needs.

whoami
The acting identity, its access level, and what that level allows. Viewer+
list_forms · get_form
All forms with field schemas / one form in full detail. Viewer+
create_form · update_form · delete_form
Create or reshape form schemas; delete removes the form and its records. Admin
create_app
One-shot hub page: title, intro, and validated navigation links/buttons to existing forms and boards — no repeated field edits needed. Admin
list_records · get_record · get_record_history
Search/paginate records, fetch one with its schema and card placements, read the audit log. Viewer+
create_record · update_record
Create records (fires the form's webhooks, lands on its default board) and merge-update field values. Editor+
delete_record
Permanently delete a record with its files and comments. Admin
list_boards · get_board
Boards with columns / one board with all its cards. Viewer+
create_board · add_card_to_board · move_card
Create a board, place a record on a board, advance cards through columns. Editor+
remove_card
Take a card off a board (the record survives). Admin
list_comments · add_comment · update_comment · delete_comment
Read and write record comments (reads Viewer+, writes Editor+; agents' comments are attributed to the key).
list_files · upload_file · download_file · delete_file · create_file_folder
Read and write file attachments — upload text or base64, download returns text or base64 (reads Viewer+, writes Editor+).

Example conversations

Once connected, you talk to your data naturally:

You: How many new leads came in this week?
Claude: Let me check... You received 23 leads this week, up from 14 last week.
        The most common source was the website contact form.

You: Move the lead from Alice Johnson to the "Qualified" column.
Claude: Done. Alice Johnson's lead is now in the Qualified column.

You: Create a new contact: Bob Smith, bob@example.com, interested in enterprise plan.
Claude: Created. Record ID rec_8f2c9a for Bob Smith has been added to Contacts.

n8n AI agent integration

If you use n8n for automation, you can expose Snapi to n8n's built-in AI agent node via the REST API. Add Snapi as an HTTP Request tool in your n8n AI agent workflow:

  1. In n8n, create an AI Agent node.
  2. Add an HTTP Request Tool with the base URL https://api.snapi.ca/api/v1.
  3. Set Authorization: Bearer snapi_... as a fixed header.
  4. Describe the tool to the agent: "Use this to read and write Snapi records. GET /entities/:id/records to list, POST /entities/:id/records to create."
!
Plan limits apply. Records created by AI agents count toward your monthly submission quota (1,000/month on Free, 10,000 on Starter, 50,000 on Team). See Plans & limits.

Security considerations