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.
Slideform MCP server
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.
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.
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.
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.
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.
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
The same work you do in the Slideform app, available to your assistant. A few of the tools it uses most:
See which reports exist, what inputs they expect, and create a new project from a template deck.
list_projectsdescribe_projectcreate_projectRun one report or many at once, fetch the finished file, and see exactly which slide failed and why.
run_projectbulk_rundownload_resultget_job_errorsPull in saved Analyst insights, look up how-to answers from the product manual, and check your remaining usage.
list_insightssearch_slideform_docsget_usageSet up
All you need is a Slideform API token from Settings → API in the Slideform app. Then pick the setup that matches your client.
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'
Download the install bundle and open it. Claude Desktop asks for your API token during setup; the token is never stored in the bundle.
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"
}
}
}
}
Connect your data and templates once in Slideform, then let your assistant run, re-run, and deliver them whenever you ask.