# OAuth

Official authenticated remote MCP endpoint for Linear issues, projects, comments, and coding-agent workflows.

Linear MCP Server is Linear’s official authenticated remote MCP endpoint for agent access to issues, projects, and comments. It gives Claude, Codex, Cursor, VS Code, Windsurf, Zed, and other clients a centrally hosted way to find, create, and update Linear work items through OAuth-backed MCP without maintaining a local connector or brittle API glue.

Official Slack MCP server for approved workspace search, messaging, canvas, and user-context actions.

Slack MCP Server is Slack’s official remote MCP layer for giving approved AI clients workspace context and controlled actions. It lets agents search messages, files, users, and channels, draft or send messages, read threads, manage canvases, and authenticate through Slack OAuth while workspace admins approve integrations and normal Slack rate limits still apply.

Self-hosted proxy API for routing AI CLI accounts into OpenAI-compatible endpoints

CLIProxyAPI is an open-source Go proxy server that wraps Gemini CLI, Claude Code, OpenAI Codex, Grok Build, and related CLI account flows behind OpenAI/Gemini/Claude-compatible API endpoints. Use it carefully: it can touch OAuth sessions, auth files, logs, and provider account policies, so production use needs credential and ToS review.

Official Asana remote MCP server for project and task workflows.

Asana MCP Server is Asana's official hosted MCP endpoint for connecting compatible AI clients to Asana work data. It lets authenticated users search workspace objects, inspect and manage tasks or projects, create work items, and generate project summaries through OAuth-backed Streamable HTTP access while preserving existing Asana permissions and admin app-management controls.

Official remote MCP server for Jira and Confluence

Atlassian's official remote MCP server connects Jira and Confluence to LLM clients, IDEs, and agent platforms over OAuth, so Claude, Cursor, and other MCP-aware tools can search issues, read pages, and post updates inside the same permission boundaries users already have. As a vendor-hosted reference implementation, it standardizes the Atlassian side of remote Model Context Protocol deployments.

HubSpot's hosted MCP server for CRM data and workflows.

HubSpot MCP Server is HubSpot's hosted remote MCP server for connecting compatible AI tools to CRM data. It uses OAuth 2.1 with PKCE through MCP auth apps, then exposes HubSpot context such as contacts, companies, deals, tickets, activities, and marketing or content objects according to user permissions, granted scopes, and sensitive-data restrictions in the account.

Intercom's remote MCP server for support and Help Center context.

Intercom MCP Server is Intercom's hosted remote MCP server for connecting AI tools to Intercom workspace data. It supports the recommended Streamable HTTP endpoint, OAuth or bearer-token authentication, and tools for conversations, contacts, companies, and Help Center article workflows, with access limited by token permissions and Intercom workspace policy.

Test and debug MCP servers before they ship

Open-source platform for inspecting, debugging and regression-testing MCP servers, MCP Apps and ChatGPT apps, with OAuth and protocol conformance for local and CI workflows.

Official Notion MCP server for AI-agent workspace access

Notion MCP Server is Notion's official MIT-licensed MCP server for connecting AI assistants to Notion workspaces. It supports the vendor-backed remote OAuth path and tools designed for page, workspace, and Markdown-style operations, making it a safer default than unofficial Notion bridges for teams already using Notion for docs, projects, or internal knowledge bases.