Skip to main content

Create personal API keys and connect with the latest MCP protocol

· 2 min read
Venue.sh Team
Venue.sh Team
Venue.sh

You can now mint your own API key from Settings and point an MCP client or script at Venue.sh without filing a request with an administrator. The Venue MCP Endpoint also moved to the 2026-07-28 protocol revision.

Create and manage your own API keys​

Generate personal API keys from Settings, without waiting on a Venue.sh administrator.

  • Self-service creation - Open Settings and create a key with an optional expiry.
  • Reveal once - Venue.sh shows the key once, at creation. Copy it then.
  • Revoke anytime - Remove a key you no longer need.
  • One active key at a time - Creating a new key revokes your existing one, so only the newest key stays valid.

See Settings for where to find your account options.

Connect with the updated MCP protocol​

The Venue MCP Endpoint now speaks the 2026-07-28 MCP protocol revision.

  • Streamable HTTP transport - The primary transport for MCP clients on the current spec.
  • Legacy endpoint redirect - Venue.sh redirects clients still calling the older /sse endpoint, so most integrations keep working untouched.
  • Cache hints - Static resources such as the tools catalog now declare cache lifetimes, so your AI tool refetches them less often.

If your AI tool cannot follow redirects, update it to call /mcp directly. See Venue MCP Endpoint for connection details.

Fixes and improvements​

  • TechDocs navigation - Fixed a crash that could occur when a project's mkdocs.yml listed both index.md and README.md for the same folder. We also published a TechDocs authoring guide covering this and other common navigation pitfalls.
  • Archived agents - You can no longer edit an archived agent, so its configuration stays locked until you restore it.

See Also​

  • Settings - Manage your personal account and organization configuration.
  • Venue MCP Endpoint - Connect AI tools to your Venue.sh data over MCP.
  • TechDocs - Enable and troubleshoot TechDocs for your Components.
  • Agents - Create, manage, and archive Assistant agents.