About Xenition
Xenition MCP connects a Xenition workspace to chat, covering documents, spreadsheets, boards, forms, deployable apps, automations, and AI-generated media. The hosted remote server requires no local installation.
Key features
- 01Work with documents, decks, sheets, and boards
- 02Create and manage forms
- 03Build and deploy apps
- 04Set up scheduled automations
- 05Generate AI images, video, and voiceover
Use cases
- 01Create or edit workspace documents in chat
- 02Build and deploy an app from a workspace
- 03Schedule automations and generate media
MCP support
Xenition provides a hosted remote MCP server at https://api.xenition.com/mcp using Streamable HTTP and OAuth 2.1. It exposes workspace and media capabilities to supported MCP clients.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://api.xenition.com/mcpclaude mcp add --transport http com-xenition-api-xenition https://api.xenition.com/mcp{"mcpServers":{"com-xenition-api-xenition":{"type":"http","url":"https://api.xenition.com/mcp"}}}Open in Cursor{"servers":{"com-xenition-api-xenition":{"type":"http","url":"https://api.xenition.com/mcp"}}}Open in VS Code{"mcpServers":{"com-xenition-api-xenition":{"type":"http","url":"https://api.xenition.com/mcp"}}}{"mcpServers":{"com-xenition-api-xenition":{"serverUrl":"https://api.xenition.com/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
71| Parameter | Type | Required | Description |
|---|---|---|---|
| end | string | No | optional end, same format as start |
| notes | string | No | |
| start | string | Yes | start: YYYY-MM-DD for all-day, or YYYY-MM-DDTHH:MM for a timed event |
| title | string | Yes | the event title |
| location | string | No |
Details
From the project READMEXenition MCP
Your Xenition workspace in the chat: documents, decks, sheets, boards, forms, apps you can build and deploy, scheduled automations, and AI images, video and voiceover — over the Model Context Protocol.
This repository is the public distribution for the Xenition MCP server: the connection details, the Claude Code plugin, the skills, and the MCP Registry entry. The server itself is hosted by Xenition — there is nothing to run or install from source.
Connect
One remote address does everything:
https://api.xenition.com/mcp
It is a standard remote MCP server (Streamable HTTP, OAuth 2.1 sign-in) and works with ChatGPT, Claude, Claude Code, VS Code, Cursor and Microsoft 365 Copilot.
Claude Code
Add it as a plugin marketplace, then install the xenition plugin:
/plugin marketplace add xenition/xenition-mcp
/plugin install xenition@xenition
Or add the remote server directly:
claude mcp add --transport http xenition https://api.xenition.com/mcp
VS Code / Cursor
Add an MCP server with URL https://api.xenition.com/mcp (HTTP transport). You
will be prompted to sign in to Xenition on first use.
ChatGPT
Add https://api.xenition.com/mcp as a connector.
Claude connector directory
Use https://api.xenition.com/mcp/workspace — the same server without the AI
image, video and audio tools, which the directory does not accept. Everything
else is identical. Users who want media tools add https://api.xenition.com/mcp
as a custom connector instead.
What's in here
| Path | What it is |
|---|---|
plugin/ | the Claude Code / Claude plugin: manifest, .mcp.json, skills, and the registry entry |
plugin/registry/server.json | the MCP Registry entry com.xenition.api/xenition |
plugin/skills/ | skills that teach assistants how to use the tools |
.claude-plugin/marketplace.json | makes /plugin marketplace add resolve this repo |
See plugin/README.md for packaging and release details.
Links
- Website: https://xenition.com
- MCP Registry:
com.xenition.api/xenition
License
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.