Claude
Two clients are covered here. Claude Desktop's file paths and filesystem example come from the MCP local-server guide. Claude Code's commands come from the Claude Code MCP docs. The Figma and Chrome DevTools blocks further down use the URL or package on those registry entries. They are not copied from the client docs.
From the Claude docs
Claude Desktop's config file locations, as published in the Connect to local MCP servers guide: macOS ~/Library/Application Support/Claude/claude_desktop_config.json, Windows %APPDATA%\Claude\claude_desktop_config.json. The same guide's filesystem example is below. The paths are the guide's placeholders. This is not a server from our directory.
{
"mcpServers": {
"filesystem": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-filesystem",
"/Users/username/Desktop",
"/Users/username/Downloads"
]
}
}
}
Claude Code's remote and local commands, from the Claude Code MCP docs:
claude mcp add --transport http notion https://mcp.notion.com/mcp
claude mcp add --env AIRTABLE_API_KEY=YOUR_KEY --transport stdio airtable -- npx -y airtable-mcp-server
That page says a JSON entry with a url and no type is a configuration error, because Claude Code treats a missing type as stdio. Project config lives in .mcp.json under mcpServers. The Notion URL and the Airtable package in those two commands are Anthropic's examples, not registry entries we rechecked for this page.
Figma, remote
From the Figma registry remote. Full notes on the Figma fact sheet.
{
"mcpServers": {
"figma": {
"url": "https://mcp.figma.com/mcp"
}
}
}{
"mcpServers": {
"figma": {
"type": "http",
"url": "https://mcp.figma.com/mcp"
}
}
}claude mcp add --transport http figma https://mcp.figma.com/mcp
Chrome DevTools, local
From the Chrome DevTools npm package. Full notes on the Chrome DevTools fact sheet.
{
"mcpServers": {
"chrome-devtools": {
"command": "npx",
"args": [
"-y",
"[email protected]"
]
}
}
}{
"mcpServers": {
"chrome-devtools": {
"command": "npx",
"args": [
"-y",
"[email protected]"
]
}
}
}Every fact sheet
- Airtable
- Amplitude
- Apify
- Apollo.io
- Appwrite
- Atlassian (Jira, Confluence)
- Auth0
- AWS
- Azure (Microsoft)
- Bitget
- Brave Search
- Browser Use
- Browserbase
- Browserless
- BrowserStack
- Buildkite
- Canva
- Capawesome
- Chrome DevTools
- CircleCI
- ClickHouse
- Close
- Cloudflare
- Composio
- Containerization Assist
- Context7 (Upstash)
- Copilot Studio
- Cypress Cloud
- ElevenLabs
- Everything (reference)
- Exa
- Fetch (reference)
- Figma
- Filesystem (reference)
- Firecrawl
- Gemini Cloud Assist
- Git (reference)
- GitHub
- GitLab
- Glide
- GoCardless
- Google Android Management
- Google Bigtable
- Google Cloud Composer
- Google Cloud Datastream
- Google Cloud Firestore
- Google Cloud Memorystore
- Google Cloud Monitoring
- Google Cloud Run
- Google Cloud SQL
- Google Compute Engine
- Google Design
- Google Developer Knowledge
- Google Kubernetes Engine
- Google Maps
- Google Stitch
- GrabzIt
- Grafana
- Hugging Face
- Kochava
- LambdaTest (TestMu AI)
- Linear
- Logo.dev
- Lovable
- Lucid
- Make
- Mapbox
- MarkItDown (Microsoft)
- Medusa
- Medusa Docs
- Memory (reference)
- Metabase
- Microsoft 365 Admin
- Microsoft 365 Copilot
- Microsoft Calendar
- Microsoft Fabric
- Microsoft Graph Users
- Microsoft Learn
- Microsoft Sentinel
- Microsoft Teams
- Microsoft Word
- Mintlify
- Mintlify Docs
- monday.com
- MongoDB
- MotherDuck / DuckDB
- Mux
- Neon
- New Relic
- Nhost
- Notion
- NuGet
- Octoparse
- OneDrive and SharePoint
- OSCAL (AWS Labs)
- OVHcloud
- PagerDuty
- PayPal
- Perplexity
- Picsart
- Planning Center
- Playwright (Microsoft)
- PostHog
- Postman
- Power BI
- Prisma Postgres
- Railway
- Redis
- Roboflow
- Sentry
- Sequential Thinking (reference)
- SharePoint Lists
- Simplenote
- Snowflake
- Snyk
- SonarQube
- Sourcegraph
- Statsig
- Stripe
- Supabase
- Svelte
- Tavily
- Teamwork.com
- Terraform (HashiCorp)
- Time (reference)
- Upwork
- Vercel
- VirusTotal
- Webflow
- Wix
- WorkOS
- Xata
- Zapier