Kinsy

ai.kinsyPublished by kinsy.aiOfficial publisherv0.1.0Updated Oct 29, 2026

Finished, editable PowerPoint (.pptx) decks from a brief and your documents

VerifiedStreamable HTTPWeb executableProductivity & WorkflowMedia & Design

Overview

AI-generated overview

Kinsy turns a brief and source text into a finished, editable PowerPoint (.pptx) deck, with tools to wait, inspect, export and edit slides.

What you can do
  • Create a deck from a brief and optional text sources, returning a deck id immediately
  • Wait for a deck to finish and stream progress, then get its links
  • Check deck status and links, optionally slide images and unsupported claims
  • Get a fresh download link for the .pptx, PDF or a zip of slide images
  • Rewrite a single slide from an instruction
  • List the theme ids that deck creation accepts
When to use it
Use it when an assistant should produce presentation decks from a written brief and the user's own documents, and the user wants an editable .pptx rather than plain text. It suits hosted assistants and agents that need to generate, check and export slides within one conversation.
Requirements
A remote MCP endpoint at mcp.kinsy.ai/mcp over streamable HTTP. A Kinsy account and API key created in Settings → API keys, sent as the Authorization header in Bearer form. A Kinsy plan with credits, since deck creation and slide edits spend credits.
Before you install
Deck creation and slide editing spend Kinsy credits, so repeated calls cost money. The API key is a live secret sent in the Authorization header; keep it out of logs and shared configs. Briefs and source text are sent to the Kinsy API, which enforces credits, limits and deck ownership; the server itself stores nothing. Export links expire after one hour.

Installation

In SourceWeft

  1. Open Kinsy in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.kinsy%2Fmcp-server/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "kinsy": {
      "type": "http",
      "url": "https://mcp.kinsy.ai/mcp"
    }
  }
}

README

Kinsy MCP server

The remote Model Context Protocol server behind https://mcp.kinsy.ai/mcp. Hosted assistants and agents connect to it with a Kinsy API key and turn a brief and the user's source material into a finished, editable PowerPoint (.pptx) deck.

It is a thin client over the public Kinsy API: every call is made with the caller's own key, so credits, limits and deck ownership are enforced by the API exactly as for the CLI. The server stores nothing and holds no credentials of its own.

Tools

ToolWhat it doesChanges anything?
create_deckStarts a deck from a brief and optional sources (text). Answers at once with a deck_id.Spends credits
wait_for_deckWaits for a deck to finish (up to 540 s), streaming progress, then returns its links.No
get_deckStatus and links; optionally slide image links and the claims the sources could not back.No
export_deckA fresh one-hour download link for the .pptx, PDF, or a zip of slide images.No
edit_slideRewrites one slide from an instruction.Spends credits
list_themesThe theme ids create_deck accepts.No

Results are a short sentence plus structured content. The server never echoes a brief or source text back, and never includes the key.

Connect

Create a key in Settings → API keys on kinsy.ai, then point your client at https://mcp.kinsy.ai/mcp with the header Authorization: Bearer ksy_live_…. Per-client instructions: kinsy.ai/docs/mcp.

Develop

bash
python3 -m venv .venv && .venv/bin/pip install -r requirements.lock pytest.venv/bin/python -m pytestKINSY_MCP_SERVE=1 KINSY_API_BASE=https://kinsy.ai .venv/bin/uvicorn kinsy_mcp.server:app --port 8080

requirements.in lists the direct dependencies; scripts/lock.sh resolves the hash-pinned requirements.lock the image installs.

MIT. © Kinsy.

Source: mcp/README.md at commit ce4d50b

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.0LatestOct 29, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts