Connecting AI Assistants (MCP)

Connect Shorty to Claude, ChatGPT, or any other AI assistant — it can then search your summaries and create new ones for you, right inside the chat. Shorty runs a remote MCP (Model Context Protocol) server, so assistants like Claude Code and Claude.ai custom connectors can use Shorty on your behalf. You sign in to Shorty once and approve exactly what the assistant may do, and you can cut it off again at any time.

Endpoint

https://aishorty.com/api/mcp

The server speaks streamable HTTP and authenticates with OAuth 2.1 and PKCE, or with a Shorty API key (shk_live_…) sent as a bearer token. Clients register automatically (unauthenticated Dynamic Client Registration), you sign in with your normal Shorty account, and a consent screen shows the permission groups the assistant is requesting before anything is granted. All groups are ticked by default; untick any you do not want the assistant to have. A key carries the permission groups you chose when you created it, and keys are managed in Settings → API keys. Session cookies are rejected on this endpoint.

Marketplaces whose tenant admins cannot register a client themselves (Microsoft 365 Copilot, Gemini Enterprise) get a static confidential client instead: the operator lists it in the OAUTH_STATIC_CLIENTS environment variable (client id, secret, name, exact redirect URIs, token-endpoint auth method) and every deployment upserts it into the same client table at boot. Such a client authenticates with its secret, may skip PKCE unless it asks for offline_access, never expires, and stays registered if it is later removed from the variable.

Connect from any MCP client

The Claude button opens the directory listing; the others install directly or jump to the instructions.

Shorty's MCP server is a hosted Streamable HTTP endpoint with OAuth 2.1 sign-in. There is nothing to install or run: point the client at the endpoint above and sign in to Shorty when the browser opens. Every client that supports remote MCP servers with OAuth works; the ones below are the common ones.

Claude (claude.ai, Claude Desktop, Claude Code)

• claude.ai / Claude Desktop: open Shorty in the Claude connector directory and click Connect, then sign in. Manual alternative: Settings → Connectors → Add custom connector, paste the URL, then sign in.
• Claude Code: claude mcp add --transport http shorty https://aishorty.com/api/mcp then /mcp to sign in.

ChatGPT and Codex

• ChatGPT: open Shorty in ChatGPT and click Connect, then sign in. Manual alternative: Settings → Apps & Connectors → Create (developer mode), name it Shorty, paste the URL, authentication OAuth.
• Codex CLI: add to ~/.codex/config.toml:

[mcp_servers.shorty]
url = "https://aishorty.com/api/mcp"

Cursor

One click: Add to Cursor. Or in .cursor/mcp.json:

{ "mcpServers": { "shorty": { "url": "https://aishorty.com/api/mcp" } } }

VS Code and GitHub Copilot

One click: Add to VS Code. Or run MCP: Add Server → HTTP and paste the URL, which writes to .vscode/mcp.json:

{ "servers": { "shorty": { "type": "http", "url": "https://aishorty.com/api/mcp" } } }

Google Antigravity

Install the plugin from the repository (or from the Antigravity Marketplace once listed):

agy plugin install https://github.com/DevinoSolutions/mcp-servers/antigravity-plugins/shorty

Or add the server by hand in ~/.gemini/config/mcp_config.json (Antigravity requires the serverUrl key):

{ "mcpServers": { "shorty": { "serverUrl": "https://aishorty.com/api/mcp" } } }

Gemini

• Gemini app: Settings → Connected apps → Custom apps → Add a custom app, paste the URL, then mention @Shorty in a chat. (Custom apps are currently limited to personal Google accounts in the US.)
• Gemini CLI: gemini extensions install https://github.com/DevinoSolutions/mcp-servers then /mcp auth shorty, or add { "mcpServers": { "shorty": { "httpUrl": "https://aishorty.com/api/mcp" } } } to ~/.gemini/settings.json.

Kiro

One click: Add to Kiro. Or in .kiro/settings/mcp.json:

{ "mcpServers": { "shorty": { "url": "https://aishorty.com/api/mcp" } } }

Perplexity, Mistral Le Chat, Grok

• Perplexity (Pro, Max, Enterprise): Settings → Connectors → Custom connector, paste the URL, authentication OAuth.
• Mistral Le Chat (all plans): Intelligence → Connectors → Add Connector → Custom MCP Connector, paste the URL.
• Grok: grok.com → Connectors → New connector → Custom, paste the URL.

Other clients

• Replit: Add to Replit, or Integrations → Add MCP server.
• Devin, Windsurf, Zed, JetBrains Junie, Cline, OpenCode: add a remote (HTTP) MCP server with the URL above; each prompts for the OAuth sign-in on first use. Cline can also install it from the Cline marketplace entry using its llms-install.md.

Tokens are scoped to what you approve on the consent screen; a tool you did not grant is never shown to the assistant. Revoke access at any time — see Managing connected apps below.

Permission groups and scopes

Scopes are grouped into permission groups (tiers). The consent screen and the API-key form show one switch per group, all on by default, with the individual scopes listed under each. A group you leave off is invisible to the assistant, and a refused call names the group to ask for through request_scopes, which returns a one-time link to approve it.

Shorty has no teams or workspaces, so there is no team group. Every operation acts on your own account.

Available tools

Shorty's MCP server lists every operation as its own tool on the directory surface and through Code Mode elsewhere. Code Mode lists two tools, search_tools and execute_typescript, instead of one tool per operation. Each operation runs the same scope, consent, quota and audit checks as a direct call, so Code Mode never lets an assistant do more than you approved. Operations are scope-filtered: an operation only appears if you granted its scope. list_granted_scopes and request_scopes appear for every connection.

What the assistant can do

Confirmations, choices and links

• Confirmation. Destructive operations (deleting a summary, transcription, account, API key, webhook or converter job, cancelling or refunding a subscription, disconnecting an app, removing a sign-in method) answer CONFIRMATION_REQUIRED with a confirmToken the first time. The assistant tells you what will happen and repeats the call with the token. A token is single-use, expires after 10 minutes and is bound to your account, the connection, the tool and the arguments.
• Choices. Plan, billing period, API-key permission groups, which item to delete and similar decisions are asked of you, never guessed.
• Links. Upgrading, managing a subscription, downloads, uploads and reconnecting with new permissions return a single-use link that opens signed in as you. Links expire after 15 minutes.
• Refusals. Every refusal carries a next object naming the tool to call, for example request_scopes.
• Audit. Every tool call is recorded with the tool, permission group, connection and a hash of the arguments, never the arguments themselves. Deleting your account removes the link between those records and you.

Write operations that start jobs are quota-gated compute jobs (they respect the same plan quotas as the web app and API) and support an optional idempotency key so retries never create duplicate jobs.

Managing connected apps

Open Settings → Connected Apps to review every assistant you have connected, and revoke any of them to cut off its access instantly. Revoking removes both the consent and the app's issued tokens, so the app must ask for your approval again to reconnect.

Connecting an MCP client is subject to Shorty's privacy policy and terms of service.