MCP · Model Context Protocol
Sliqtly for AI assistants
Connect Sliqtly to your assistant and ask it for a presentation. It writes the slides in Markdown, picks a theme, adds CSS, pictures, charts and diagrams, and gives you a link that opens the finished presentation.
https://sliqtly.com/mcpRunning Sliqtly locally? The address is http://localhost:8080/mcp (another port if you chose one). A local server has no sign-in and nothing on it expires: every agent connected to it can change every presentation, and you keep and clean up the data yourself. See how to run it locally.
Claude claude.ai, desktop and mobile apps
Free, Pro and Max
- Open Customize → Connectors (in older versions Settings → Connectors).
- Click Add custom connector.
- Name:
Sliqtly. URL:https://sliqtly.com/mcp. - Authentication: Sign in now keeps the presentations in your own Sliqtly account (Google), so only you can change them; anyone with a link can still view them. No sign-in works too, for text only: the presentations then belong to no account, are open to anyone with their link, and are deleted 30 days after their last change. Pictures and data files need sign-in.
- Click Add, and with sign-in, Connect: a Sliqtly page asks you to continue with Google.
Team and Enterprise
An owner adds it once under Organization settings → Connectors → Add → Custom (type Web) with the same URL. Members then find it under Customize → Connectors and click Connect.
In a chat
Open the + menu → Connectors and turn Sliqtly on. The presentation appears in the conversation and its link opens it full size.
Running Sliqtly locally? Connectors added here are called from Anthropic's cloud and need an https:// address, so http://localhost:8080/mcp is refused. In Claude Desktop, add the server to its config file through mcp-remote instead. claude.ai on the web and the mobile apps reach it only through a public HTTPS tunnel, which opens your server to the internet (Claude apps and a local server).
Claude Code
claude mcp add --transport http sliqtly https://sliqtly.com/mcp
Add --scope user to have it in every project.
Running Sliqtly locally? claude mcp add --transport http sliqtly http://localhost:8080/mcp (how to run it locally).
ChatGPT Plus, Pro, Business, Enterprise, Edu; web
- Open Settings → Apps & Connectors → Advanced settings and turn on Developer mode. On Business and Enterprise a workspace owner has to allow it first.
- Back in Apps & Connectors, click Create.
- Name:
Sliqtly. Description: Makes slide presentations from Markdown. MCP server URL:https://sliqtly.com/mcp. Authentication: OAuth to keep the presentations in your own Sliqtly account, or No authentication. - Tick that you trust the application and click Create. With OAuth, ChatGPT then opens the Sliqtly sign-in page.
In a new chat, open + → Developer mode (or More) and choose Sliqtly. ChatGPT asks before it makes a presentation; allow it.
The menu names move between ChatGPT versions. If you do not find Developer mode under Apps & Connectors, look under Settings → Connectors → Advanced.
Running Sliqtly locally? ChatGPT runs in the cloud and cannot reach a server on your computer; use one of the local clients below with http://localhost:8080/mcp (how to run it locally).
OpenAI API Responses API, Agents SDK
{
"type": "mcp",
"server_label": "sliqtly",
"server_url": "https://sliqtly.com/mcp",
"require_approval": "never"
}
Put it in the request's tools list. In the Agents SDK use HostedMCPTool with the same tool_config.
Running Sliqtly locally? OpenAI calls the server from its own cloud, so it needs an address reachable from the internet (behind a proxy with HTTPS and SLIQTLY_TOKEN), not localhost (how to run it locally).
Cursor
Settings → Tools & MCP → New MCP server, or add this to ~/.cursor/mcp.json (every project) or .cursor/mcp.json (one project):
{
"mcpServers": {
"sliqtly": {
"url": "https://sliqtly.com/mcp/account"
}
}
}
Cursor signs in only when the server asks, and /mcp/account asks: Cursor shows Needs login (or Connect) next to Sliqtly; click it and continue with Google. Your presentations, topics and folders are then the account's. https://sliqtly.com/mcp works without sign-in, for text-only presentations.
In Agent mode, ask for a presentation; Cursor asks before calling the tool.
Running Sliqtly locally? Use "url": "http://localhost:8080/mcp" (how to run it locally).
Other MCP clients
Any client that speaks MCP over Streamable HTTP works with the URL above. They connect without sign-in; clients that support MCP's OAuth sign-in can also sign in. A client that signs in only when the server asks (as Cursor does) signs in at https://sliqtly.com/mcp/account.
VS Code (GitHub Copilot)
// .vscode/mcp.json
{
"servers": {
"sliqtly": { "type": "http", "url": "https://sliqtly.com/mcp" }
}
}
Windsurf
// ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"sliqtly": { "serverUrl": "https://sliqtly.com/mcp" }
}
}
Gemini CLI
// ~/.gemini/settings.json
{
"mcpServers": {
"sliqtly": { "httpUrl": "https://sliqtly.com/mcp" }
}
}
Running Sliqtly locally? Replace https://sliqtly.com/mcp with http://localhost:8080/mcp in each of these (how to run it locally).
A client that only runs local servers
npx -y mcp-remote https://sliqtly.com/mcp
Running Sliqtly locally? npx -y mcp-remote http://localhost:8080/mcp (how to run it locally).
Using it
Ask in your own words, for example:
Make a risk analysis of the latest pull request in our repository: describe the data models it changes and the critical spots in the code.
Add a slide with a diagram of how the changed models relate, and mark the riskiest change in red.
Sliqtly is provided as is, and you store data in it at your own risk.