SLIDESPOKEN MCP

Connect any AI assistant to SlideSpoken

Let Claude, Cursor, Hermes, OpenClaw and other MCP-compatible agents securely access and manage your SlideSpoken presentations.

MCP server URL

https://slidespoken.com/api/mcp

Open SlideSpoken

No API key required for supported OAuth clients.
Sign in with your SlideSpoken account and approve access.

HOW IT WORKS

Four steps, no secret to copy

1
Copy the MCP URL
One address, the same for everyone.
2
Add it to your AI assistant
Paste it into a compatible client.
3
Sign in to SlideSpoken
Your browser opens automatically.
4
Approve access
Review what the assistant may do, then Allow.

SlideSpoken uses OAuth 2.1 with PKCE. The assistant receives a scoped authorization for your account — never your password, and never a credential you had to copy by hand.

CAPABILITIES

What your AI assistant can do

VIEW

List your presentations
View presentation details
View scheduled presentations
View session results and Q&A

ACT

Schedule Agent Mode presentations
Update a scheduled presentation
Cancel a scheduled presentation

IMPORT

Import a PDF or PowerPoint
Import from a direct HTTPS link
Reuse a presentation you already have

There is deliberately no tool that starts a live presentation. An assistant can schedule and change sessions; beginning one stays a decision you make yourself.

IMPORT

Bring your presentations with you

Supported sources

PDF (.pdf)
PowerPoint (.pptx)
A direct HTTPS link that downloads the file itself
A presentation already in your account

Maximum file size: 50 MB
Maximum pages / slides: 60

Other formats — .ppt, Keynote, Google Slides, Word documents and images — are not supported by the importer.

A file on your computer

An AI assistant cannot hand a binary file through a conversation, so SlideSpoken gives you a secure upload link instead.

1Ask your assistant to import a presentation.
2Open the secure SlideSpoken upload link it returns.
3Upload your PDF or PowerPoint file.
4Your assistant continues once the import is ready.

Imports take a little time. Your assistant keeps the import reference and checks its status, and only uses the presentation once processing has actually finished.

SUPPORTED CLIENTS

Set up your AI assistant

Claude Code

Verified

Connected end to end with no API key. We completed this flow ourselves, including on a remote server.

1Run the add command below.
2Start Claude Code, then run /mcp and choose slidespoken → Authenticate.
3Your browser opens: sign in to SlideSpoken and click Allow access.
4Run claude mcp list — slidespoken shows as Connected.

terminal

claude mcp add --transport http slidespoken https://slidespoken.com/api/mcp

claude
# then inside Claude Code:
/mcp   →  slidespoken  →  Authenticate

claude mcp list

Using Claude Code on a remote server?

After approving access, your browser may show “localhost refused to connect.” This is expected: localhost refers to your own computer, while Claude Code is running on the remote server.

Copy the full callback URL from your browser address bar and paste it into Claude Code to complete authentication.

Verified — this is the tested behaviour.

COMPATIBILITY

Where SlideSpoken MCP stands today

CLIENT	STATUS	AUTH METHOD	WRITE TOOLS	VERIFIED
Claude Code	Verified	OAuth 2.1 (URL only)	Yes	Yes
Claude Desktop	Supported — verification pending	OAuth 2.1 (URL only)	Yes	No
Hermes Agent	Supported — verification pending	OAuth 2.1 (URL only)	Yes	No
OpenClaw	Supported — verification pending	OAuth 2.1 (URL only)	Yes	No
Cursor	Supported — verification pending	OAuth 2.1	Yes	No
ChatGPT	Limited	OAuth 2.1, via developer mode	Plan dependent	No
Manus	Not currently verified	Unconfirmed	Unconfirmed	No
xAI / Grok	Limited	Custom connector; OAuth unconfirmed	Yes, once connected	No
Any MCP client	Supported — verification pending	OAuth 2.1 + PKCE (S256)	Yes	No
Developer / custom	Supported — verification pending	Personal access token (ssk_)	Yes	No

Verified means we completed the flow ourselves, end to end. Everything else reflects each vendor's own current documentation — we would rather tell you a client is unproven than have it fail on you.

SHORTCUT

Ask your agent to connect itself

If your assistant can configure its own MCP servers, paste this in and let it do the work.

Connect my AI agent to SlideSpoken using its remote MCP server:

https://slidespoken.com/api/mcp

Use standards-compliant remote MCP over Streamable HTTP and OAuth.

Do not ask me to create or paste an API key unless this client does not support OAuth.

Discover the server's OAuth configuration automatically, register the client if required, and start the authorization flow.

When the browser opens, let me sign in to my SlideSpoken account and approve access.

After authentication, verify the SlideSpoken MCP tools are available and then list my SlideSpoken presentations.

If this agent is running on a remote server and the localhost OAuth callback cannot connect, show me the callback URL workflow rather than abandoning the authorization.

Do not make any presentation changes until I explicitly ask.

AFTER CONNECTING

Things to try

“List my SlideSpoken presentations.”
“Show my scheduled presentations.”
“Schedule my Quarterly Sales Review tomorrow at 10 AM Qatar time using Google Meet and invite john@example.com.”
“Move tomorrow’s presentation to 2 PM.”
“Cancel the presentation scheduled for Friday.”
“Show me the summary and Q&A from my latest presentation.”
“Import this PDF into SlideSpoken: https://example.com/deck.pdf”
“Upload my presentation and schedule it for Friday.”

PERMISSIONS

Exactly what you are approving

A connected assistant can

View your presentations
View scheduled presentations
Create Agent Mode schedules
Update schedules
Cancel schedules
View session summaries and results
Import presentations into your account

It cannot

Access another SlideSpoken account
Bypass your plan or credit limits
Start Training Mode — it is coming soon
Start a live presentation
Obtain your SlideSpoken password
Receive your Google or Zoom credentials

SECURITY

How the connection is protected

OAuth 2.1 with PKCE

Authorization Code flow with PKCE. Your password is never shared with the assistant.

Tokens bound to SlideSpoken

An access token is issued for the SlideSpoken MCP endpoint specifically, and is rejected anywhere else.

Signed and verified

Every token is signature-verified on each request against SlideSpoken’s published keys.

Your account only

Every tool resolves your identity from the credential. Presentation ownership is checked server-side on each call.

Plans still apply

Credit and plan limits are enforced by SlideSpoken, not by the assistant.

Revocable at any time

Disconnect an assistant from Settings and its access stops immediately.

ADVANCED

Developer access

Most people never need this. For scripts, CI jobs and clients that do not support OAuth, you can generate a personal access token in Settings → Integrations → MCP. It is shown once and stored only as a hash, so keep it somewhere safe or generate a new one.

You can disconnect assistants and revoke tokens from the same screen at any time.