Slideform MCP server

Run your reporting from Claude

Connect Claude Code, Claude Desktop, Cursor, or any other Model Context Protocol (MCP) client to Slideform. Ask for a report in plain language and get back the same editable deck your team already approved.

Ask Claude for the report you need

Once the Slideform MCP server is connected, your assistant can find projects, run them, fan one template out across many rows, and explain what went wrong when a slide comes back empty.

A thin connector, not a new copy of your data

The MCP server is a small adapter over Slideform's public REST API. It speaks the open Model Context Protocol rather than one vendor's plugin format, so it is not tied to Claude. Your projects, templates, and data connections stay in Slideform, under the same access rules your team already uses.

Never sees your data credentials

The server only carries your Slideform API token. Warehouse, BI, and CRM credentials stay inside Slideform, and the connector holds no business logic of its own.

Your role, your permissions

Every call runs as the token's owner. Changes such as editing projects or bulk runs need an Editor or Admin role, and AI-powered steps that bill your account only run when you allow them.

Built for long reports

Runs return a durable job handle right away, so a large deck never outlives your client's timeout. Check on the job, then download the result when it is ready.

What your assistant can do

About 60 tools across the reporting workflow

The same work you do in the Slideform app, available to your assistant. A few of the tools it uses most:

Find and build projects

See which reports exist, what inputs they expect, and create a new project from a template deck.

  • list_projects
  • describe_project
  • create_project

Run and deliver reports

Run one report or many at once, fetch the finished file, and see exactly which slide failed and why.

  • run_project
  • bulk_run
  • download_result
  • get_job_errors

Reuse insights and get answers

Pull in saved Analyst insights, look up how-to answers from the product manual, and check your remaining usage.

  • list_insights
  • search_slideform_docs
  • get_usage

Set up

Connect in under a minute

All you need is a Slideform API token from Settings → API in the Slideform app. Then pick the setup that matches your client.

Claude Code

Use the hosted server. There is nothing to install; your token rides each request as a header.

claude mcp add --transport http slideform 'https://mcp.slideform.co/mcp' --header 'x-api-key: ta_xxx'

Claude Desktop

Download the install bundle and open it. Claude Desktop asks for your API token during setup; the token is never stored in the bundle.

Download slideform.mcpb

Cursor, Codex, and other MCP clients

Any client that supports MCP over streamable HTTP, including Cursor, Codex, and VS Code with GitHub Copilot, can connect to the hosted endpoint with an x-api-key header, or run the server locally over stdio with your token in the environment. For the hosted endpoint, many clients accept a JSON block like this one; check your client's docs for its exact file and format.

{
  "mcpServers": {
    "slideform": {
      "type": "http",
      "url": "https://mcp.slideform.co/mcp",
      "headers": {
        "x-api-key": "ta_xxx"
      }
    }
  }
}

Put your reports one prompt away

Connect your data and templates once in Slideform, then let your assistant run, re-run, and deliver them whenever you ask.