MCP & Tools

Connections to external services, APIs, and databases via Model Context Protocol

Extension Name MCP Servers
Vendor Terms MCP servers, mcp.json, MCP registry, Add to Kiro badge
Scopes
User / HomeProject / Repo RootOrganization / Enterprise
Interfaces IDE, CLI
Availability current (explicit)
Trust Model Tool calls require per-use approval unless auto-approved; enterprise registry allow-list with client-side enforcement
Notes Workspace and user configs merge with workspace precedence; CLI adds agent config as a third tier; curated server directory with 30+ servers and one-click install; enterprise MCP registry allow-list fetched at startup and every 24h
Extension Name MCP Servers
Vendor Terms MCP servers, .mcp.json, managed-mcp.json, MCP Tool Search
Scopes
User / HomeProject / Repo RootOrganization / Enterprise
Interfaces terminal CLI, VS Code, Desktop, web, JetBrains
Availability current (explicit)
Trust Model Project-scoped servers require explicit approval; enterprise lockdown via managed-mcp.json allowlist/denylist
Notes Five-tier scope hierarchy (local > project > user > plugin > claude.ai connectors); Tool Search defers tool loading until needed; supports HTTP, SSE, and stdio transports; OAuth 2.0 with scopes pinning; Claude Code can serve as an MCP server
Extension Name MCP Servers
Vendor Terms MCP servers, GitHub MCP server, MCP Registry, MCP allowlist
Scopes
Machine / AdminProject / Repo RootOrganization / Enterprise
Interfaces GitHub.com, VS Code, Visual Studio, JetBrains, Eclipse, Xcode, CLI, Copilot SDK
Availability current (explicit)
Trust Model Tool calls subject to OAuth/PAT auth and allowlist enforcement; enterprise policies override org policies
Notes Available on all surfaces regardless of plan; GitHub MCP Registry in public preview; org/enterprise can restrict via allowlist policy; cloud agent integrates with Jira, Slack, Teams, Linear, and Azure Boards via MCP
Extension Name MCP Servers
Vendor Terms MCP servers, OAuth authentication
Scopes
User / HomeProject / Repo Root
Interfaces CLI, IDE extension, app
Availability current (explicit)
Trust Model Destructive tool calls always require approval; enterprise allowlist enforces name + identity matching
Notes STDIO and streamable HTTP transports; OAuth via codex mcp login; per-server tool filtering and timeouts; enterprise allowlist via requirements.toml
Data last updated 2026-04-19 · Auto-generated from upstream docs and may be inaccurate · Source on GitHub