# Xenition [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/xenition/xenition-mcp  
**GitHub Stars:** 1  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/xenition

## Description
Docs, decks, forms, apps you build and deploy, automations, and AI images, video and voice.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "xenition": {
    "url": "https://api.xenition.com/mcp"
  }
}
```

## Documentation

## What the Xenition MCP server does

The Xenition MCP server gives AI assistants access to a Xenition workspace through Model Context Protocol. Its supported workspace scope includes documents, presentation decks, spreadsheets, boards, forms, and applications that can be built and deployed. It also exposes scheduled automations and generation tools for AI images, video, and voiceover.

The repository is a distribution and integration package rather than the server implementation. It contains connection details, a Claude Code plugin, assistant skills, and an MCP Registry entry. Xenition hosts the service itself, so developers do not build or run the repository locally.

## How it works

The Xenition MCP server is a remote Streamable HTTP service at `https://api.xenition.com/mcp`. Clients connect to that address and authenticate through OAuth 2.1. After sign-in, an assistant can use the available Xenition workspace capabilities through MCP rather than calling separate product endpoints.

The repository also publishes the registry identifier `com.xenition.api/xenition`. Its plugin package includes a manifest, MCP configuration, skills, and marketplace metadata for Claude Code and Claude-compatible plugin workflows.

## Setup and configuration

No environment variables or local process are required according to the provided setup. Add the remote server URL to a supported client and complete the Xenition sign-in prompt when requested.

Claude Code can install the published plugin through its marketplace, or add the remote endpoint directly with the HTTP transport. VS Code and Cursor use the same URL as an HTTP MCP server. ChatGPT can add the endpoint as a connector.

For a Claude connector directory, use `https://api.xenition.com/mcp/workspace`. That variant retains the rest of the workspace functionality but excludes AI image, video, and audio tools because the directory does not accept those capabilities. To use the media tools, configure the main endpoint as a custom connector instead.

## Tools and capabilities

The Xenition MCP server covers these supported areas:

- Create and work with documents, decks, sheets, boards, and forms.
- Build and deploy applications within the Xenition workspace.
- Configure scheduled automations.
- Generate AI images, video, and voiceover.
- Connect assistants to Xenition workspace operations through MCP.

The material describes capabilities by product area rather than listing individual MCP tool names, so exact tool identifiers are not specified here.

## Limitations and notes

The service is hosted by Xenition; the public repository does not provide a self-hosted server to run from source. OAuth 2.1 sign-in is part of the remote connection flow. The `/workspace` endpoint is intended for the Claude connector directory and omits image, video, and audio functionality. Use the primary `/mcp` endpoint when those media capabilities are needed.

The README names ChatGPT, Claude, Claude Code, VS Code, Cursor, and Microsoft 365 Copilot as supported connection environments. This listing uses client identifiers where an available compatibility slug matches those names.

_Full upstream README: https://allmcps.com/mcp/xenition/readme_