Corcava logo Le seul outil métier dont vous avez besoin Corcava
Menu
Solutions
Secteurs
Designers RH & recrutement Cabinets d'avocats Immobilier Conseil Marketing digital Comptabilité E‑commerce Développement logiciel
Produit
Fonctionnalités Intégrations
Blog Télécharger
Ressources
Templates Docs MCP FAQ API Comparaisons Feuille de route Quoi de neuf $ Programme d'affiliation
Tarifs
Essai gratuit de 14 jours

Aucune carte bancaire requise

Générateur de config MCP Corcava : Claude, Cursor, Windsurf, Continue

Générez des extraits de configuration MCP à copier-coller pour votre assistant IA. Modèles de config prêts à l'emploi pour Claude Desktop, Cursor, Windsurf et Continue, avec bonnes pratiques de sécurité et stockage des clés API.

Comment utiliser ce générateur

Suivez ces étapes pour générer votre configuration MCP :

Interface du générateur (spécification texte)

Spécification texte d'un générateur de config interactif. En implémentation complète, les champs seraient :

  • Sélection client : Menu ou boutons radio pour Claude Desktop, Cursor, Windsurf, Continue
  • Champ clé API : Saisie (masquée) pour votre clé API Corcava
  • Bouton Générer : Crée l'extrait de config selon les sélections
  • Affichage sortie : Affiche le JSON généré prêt à copier

Modèles de configuration par client

Claude Desktop

Modèle de config Claude Desktop

Location: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows)

{ "mcpServers": { "corcava": { "command": "npx", "args": [ "-y", "@modelcontextprotocol/server-http", "https://mcp.corcava.com" ], "env": { "CORCAVA_API_KEY": "YOUR_API_KEY_HERE" } } } }

Replace: YOUR_API_KEY_HERE with your actual Corcava API key

Cursor

Cursor Config Template

Location: ~/.cursor/mcp.json

{ "mcpServers": { "corcava": { "url": "https://mcp.corcava.com", "headers": { "Authorization": "Bearer YOUR_API_KEY_HERE" } } } }

Replace: YOUR_API_KEY_HERE with your actual Corcava API key

Windsurf

Windsurf Config Template

Location: Windsurf Settings → AI → MCP Servers

{ "name": "corcava", "serverUrl": "https://mcp.corcava.com", "headers": { "Authorization": "Bearer YOUR_API_KEY_HERE" } }

Replace: YOUR_API_KEY_HERE with your actual Corcava API key

Continue

Continue Config Template

Location: ~/.continue/config.json

{ "mcpServers": [ { "name": "corcava", "url": "https://mcp.corcava.com", "type": "sse", "headers": { "Authorization": "Bearer YOUR_API_KEY_HERE" } } ] }

Replace: YOUR_API_KEY_HERE with your actual Corcava API key

Note: Continue uses SSE transport for remote MCP servers

Security and Key Storage

⚠️ Security Best Practices

  • Never commit API keys: Add config files to .gitignore if storing in version control
  • Use environment variables: Some clients support env vars instead of hardcoding keys
  • Separate keys per client: Create different API keys for each client/machine for better security
  • Rotate regularly: Set a schedule to rotate API keys (e.g., every 90 days)
  • Revoke compromised keys: Immediately revoke any key that may be exposed

Using Environment Variables

For better security, some clients support environment variables:

Example: Cursor with Environment Variable

{ "mcpServers": { "corcava": { "url": "https://mcp.corcava.com", "headers": { "Authorization": "Bearer ${CORCAVA_API_KEY}" } } } }

Note: ~/.cursor/mcp.json may not reliably expand environment variables. For better compatibility, use an "env" object instead:

{ "mcpServers": { "corcava": { "url": "https://mcp.corcava.com", "env": { "CORCAVA_API_KEY": "YOUR_API_KEY_HERE" }, "headers": { "Authorization": "Bearer ${CORCAVA_API_KEY}" } } } }

Then set the environment variable:

# macOS/Linux export CORCAVA_API_KEY="your_key_here" # Windows (PowerShell) $env:CORCAVA_API_KEY="your_key_here"

Benefits: Key not stored in config file, easier to rotate, better for teams

Quick Copy-Paste Configs

Claude Desktop (Quick Copy)

{ "mcpServers": { "corcava": { "command": "npx", "args": ["-y", "@modelcontextprotocol/server-http", "https://mcp.corcava.com"], "env": {"CORCAVA_API_KEY": "YOUR_API_KEY_HERE"} } } }

Replace YOUR_API_KEY_HERE with your key

Cursor (Quick Copy)

{ "mcpServers": { "corcava": { "url": "https://mcp.corcava.com", "headers": {"Authorization": "Bearer YOUR_API_KEY_HERE"} } } }

Replace YOUR_API_KEY_HERE with your key

Windsurf (Quick Copy)

{ "name": "corcava", "url": "https://mcp.corcava.com", "headers": {"Authorization": "Bearer YOUR_API_KEY_HERE"} }

Replace YOUR_API_KEY_HERE with your key

Continue (Quick Copy)

{ "mcpServers": [{ "name": "corcava", "url": "https://mcp.corcava.com", "type": "sse", "headers": {"Authorization": "Bearer YOUR_API_KEY_HERE"} }] }

Replace YOUR_API_KEY_HERE with your key

Verification Steps

After adding the config, verify it works:

Verification Checklist

  1. Restart your MCP client completely
  2. Check that Corcava MCP server appears in available servers
  3. Test with a simple prompt: "List my projects from Corcava"
  4. Verify tools are available (list_tasks, create_task, etc.)

Troubleshooting

Config Not Working

Symptom: MCP server doesn't appear after adding config

Fix:

  • Verify JSON syntax is valid (no trailing commas, proper quotes)
  • Check config file is in correct location
  • Ensure client was fully restarted (not just reloaded)
  • See Config JSON Errors

Auth Errors

Symptom: 401 Unauthorized errors

Fix:

  • Verify API key is correct and active
  • Check Authorization header format: "Bearer YOUR_KEY"
  • Ensure no extra spaces in the key
  • See 401 Troubleshooting

Related Resources

Claude Desktop Setup

Detailed setup guide

Cursor Setup

Detailed setup guide

API Key Management

Best practices for keys

Config Troubleshooting

Fix config errors

Generate Your MCP Config

Use these templates to quickly set up Corcava MCP in your AI assistant

Get Started → API Key Guide