Model Context Protocol

Give any AI agent the power to build presentations.

SlideForge runs a hosted, spec-compliant MCP server. Connect Claude, ChatGPT, or any MCP-compatible client or agent framework, and let it generate, check on, and export PowerPoint presentations directly through a user's SlideForge account.

Connect an agent Full API reference

Endpointhttps://mcp.slideforge.io/mcp

TransportStreamable HTTP

AuthOAuth 2.1 + PKCE

Tools6 tools

Overview

What is MCP?

The Model Context Protocol (MCP) is an open standard for connecting AI assistants and agents to external tools and data sources over a common protocol, instead of a bespoke integration per platform. A client (an AI model, assistant, or agent runtime) discovers a server's capabilities and calls them as typed tools.

SlideForge's MCP server is a thin, read-through adapter over our public presentation API: every tool call forwards the connected user's own SlideForge account credentials, so an agent can act on that user's behalf - using their templates, their credit balance, their presentation history - without SlideForge ever handling a shared or service-level API key.

Connect

Connect in a minute.

Step 1

Add the connector

In Claude, ChatGPT, Grok (grok.com/connectors, then New Connector, then Custom), or your MCP client's connector/integrations settings, add a new remote MCP server using the endpoint below.

https://mcp.slideforge.io/mcp

Step 2

Sign in & authorize

Your client redirects to SlideForge to sign in (password, Google, or Apple) and approve access - standard OAuth 2.1 with PKCE. No manual API key handling required.

Step 3

Ask your agent to build a deck

"Create a 8-slide presentation on Q3 sales performance" - your assistant calls generate_presentation, polls status, and can export the finished PPTX directly in the conversation.

For MCP clients that use a config file (e.g. Claude Desktop-style setups) rather than an in-app connector UI:

{
  "mcpServers": {
    "slideforge": {
      "url": "https://mcp.slideforge.io/mcp"
    }
  }
}

Reference

Tool reference.

Tool	What it does	Parameters	Returns
`generate_presentation`	Start generating a new presentation from a topic.	`topic, num_slides, tone, language, target_audience, layout_type`	presentation_id, status (async - poll for completion)
`check_presentation_status` read-only	Poll the generation status of a presentation.	`presentation_id`	status ("generating" \| "completed" \| "failed"), completed_at
`list_presentations` read-only	List the connected account's previously generated presentations.	`skip, limit`	array of presentation summaries
`list_templates` read-only	List presentation templates available in SlideForge.	`(none)`	array of templates with name, category, premium flag, preview url
`export_presentation` read-only	Get a direct download link for a completed presentation.	`presentation_id, format ("pptx" \| "pdf" \| "images")`	download_url (valid for a few minutes), format
`get_account` read-only	Get the connected account's slide balance and usage.	`(none)`	slides_available, slides_purchased, slides_used, subscription_status

Generation is asynchronous: generate_presentation returns immediately, and a client should poll check_presentation_status until it reports completed before calling export_presentation.

Authentication

How auth works.

The SlideForge MCP server implements the MCP specification's OAuth 2.1 resource-server flow. An unauthenticated request to the endpoint returns 401 with a WWW-Authenticate header pointing to protected-resource metadata, which names SlideForge's authorization server. Most MCP clients complete this discovery and the login/consent screen automatically.

Protected resource metadata

https:/.slideforge.io/mcp/.well-known/oauth-protected-resource/mcp

Authorization server metadata

https://app.slideforge.io/.well-known/oauth-authorization-server

Dynamic client registration

https://app.slideforge.io/oauth/register
RFC 7591 - platforms self-register, no manual credential setup.

Sign-in methods

Password, Google, or Apple - same identity providers as the web and mobile apps.

FAQ

Frequently asked questions.

What is the SlideForge MCP server endpoint?

SlideForge's hosted MCP server is available at https://mcp.slideforge.io/mcp, using the Streamable HTTP transport. Any MCP-compatible client - Claude, ChatGPT, or a custom agent built with the MCP SDK - can connect directly to this URL.

How do I authenticate with the SlideForge MCP server?

SlideForge's MCP server implements the MCP OAuth 2.1 resource-server flow with PKCE. When a client connects without a token, it receives a 401 response with a WWW-Authenticate header pointing at the protected-resource metadata, which in turn points at the authorization server (https://app.slideforge.io). Most MCP clients handle this discovery and the login/consent screen automatically. Dynamic client registration (RFC 7591) and Client ID Metadata Documents are both supported, so platforms do not need to pre-register credentials.

How do I use SlideForge in Grok?

In Grok, open grok.com/connectors, choose New Connector, then Custom, and enter https://mcp.slideforge.io/mcp. Grok sends you to SlideForge to sign in and approve access. After that, ask Grok to make a presentation and it uses SlideForge's tools.

Do I need a SlideForge account to use the MCP server?

Yes, a free SlideForge account is required. Signup includes free trial slide credits, so a new user can generate their first presentation through an MCP client immediately after connecting, with no payment required upfront.

What can an AI agent do with the SlideForge MCP server?

An agent can generate a new presentation from a topic, poll its generation status, list a user's past presentations and available templates, export a completed presentation as PPTX, PDF, or a ZIP of slide images, and check the connected account's slide balance.

Is presentation generation synchronous or asynchronous over MCP?

Asynchronous. generate_presentation returns immediately with a presentation ID and an in-progress status, since generation runs in the background on SlideForge's servers. An agent should call check_presentation_status every few seconds until the status becomes "completed" (or "failed") before calling export_presentation.

Where can I find the underlying REST API documentation?

The MCP server is a thin adapter over a public REST API. Full interactive API documentation is published at https://app.slideforge.io/docs (Swagger UI), https://app.slideforge.io/redoc, and the raw OpenAPI schema at https://app.slideforge.io/openapi.json.

Developers

Ready to connect your agent?

Create a free SlideForge account, then point any MCP client at https://mcp.slideforge.io/mcp.

Get started free Explore all features

First 7 days $0 · Cancel anytime · Export to PPTX