Skip to main content

MCP for AI agents

The Model Context Protocol (MCP) is an open standard for giving AI assistants safe, structured access to tools and data. Instead of writing glue code, you point an assistant like Claude at an MCP server and it can discover the available tools and call them on your behalf. imatic products expose MCP servers so an agent can do real work — check availability and book a meeting, submit and summarize survey responses, run a live poll — using your account's permissions.

What MCP gives you​

  • Tool discovery — the assistant asks the server what it can do and gets a typed list of tools, so you don't hand-write integrations.
  • Real actions, not just chat — tools read and write your actual data (within the scopes you grant).
  • One protocol, many products — the same connection pattern works for Calendar, Survey, and Voice Portal.

Which tools each product exposes​

Calendar​

Calendar ships a production MCP server with 7 tools:

  • list_event_types — list the meeting types you offer.
  • list_slots — find open slots for an event type in a time window.
  • create_booking — book a slot for an invitee.
  • cancel_booking — cancel a booking.
  • reschedule_booking — move a booking to a new time.
  • list_bookings — list existing bookings.
  • get_booking — read a single booking by id.

This makes Calendar a natural fit for an AI scheduling assistant: it can discover your event types, check real availability, and book without double-booking. See Calendar for developers.

Survey​

Survey runs a live MCP server at POST /mcp (JSON-RPC 2.0) with 10 tools for working with forms, responses, and polls:

  • whoami — identify the authenticated caller and organization.
  • list_forms — list the forms in your organization.
  • get_form — read a single form's structure.
  • submit_response — submit a response to a form.
  • list_responses — list responses for a form.
  • get_response — read a single response.
  • get_response_stats — aggregate response statistics for a form.
  • create_poll — create a quick poll.
  • cast_vote — cast a vote in a poll.
  • live_poll_results — read a poll's live tally.

See Survey for developers.

Voice Portal​

Voice Portal approaches MCP from the other direction: instead of (only) being an MCP server, it lets you register external MCP servers so your voice agents can use their tools during a call. In the portal, go to Integrations → MCP Servers to register a server, store its credentials, discover its functions, and bind those tools to an agent. See Tools & MCP for agents.

Transport​

The Calendar MCP supports both HTTP and stdio, so you can connect either a remote assistant or a local one; the Survey MCP is HTTP (JSON-RPC) only.

  • HTTP — the assistant connects to the server's /mcp endpoint over HTTPS. Use this for hosted/remote agents.
  • stdio — the server runs as a local process the assistant launches and talks to over standard input/output. Use this for local desktop tools.

Authentication and isolation​

The credential an MCP server expects depends on the product:

  • Calendar — authenticates with a scoped API key that carries the mcp scope, sent as a Bearer token. The key's scopes still bound what each tool call can do, and calls are confined to the key's organization. Mint a dedicated key per agent in Developers → API keys.
  • Survey — authenticates with your portal JWT (a session token), sent as a Bearer token. The token's organization scopes every call, so an agent only ever sees that organization's forms and responses.
  • Voice Portal — you don't authenticate to a Voice MCP server; instead you register external MCP servers in the portal and store their credentials there (see below).

In every case, calls are confined to the account or organization the credential belongs to — an agent can't reach another customer's data.

Give agents the narrowest credential

For Calendar, create a dedicated API key for each agent with only the scopes it needs, and remember the key is shown only once at creation — copy it then. If an agent misbehaves or its key leaks, revoke that key in the developer area without affecting your other integrations.

Connect from Claude​

MCP clients (such as Claude Desktop) read a small JSON config that tells them how to reach a server. The shape below is illustrative — use the exact endpoint and any flags from the product's developer page, and paste in an API key you created for this purpose:

{
  "mcpServers": {
    "imatic-calendar": {
      "url": "https://<calendar-host>/mcp",
      "headers": {
        "Authorization": "Bearer cal_abc123.s3cr3t_keymaterial"
      }
    }
  }
}

For a local (stdio) connection, the client launches the server command instead of connecting to a URL — again, follow the product's developer page for the exact command. Once connected, ask the assistant what tools it has; for Calendar it should report the seven tools listed above, and you can ask it to, for example, "find my next free 30-minute slot and book it for alex@example.com."