Skip to main content

Creating Servers

Learn how to create and manage MCP servers in Reeva.

What is a Server?​

A server is a collection of custom tools exposed through the MCP protocol. Each server:

  • Has a unique ID and name
  • Contains multiple custom tools
  • Can be accessed via API keys
  • Works with any MCP-compatible IDE

Creating Your First Server​

Via Dashboard​

  1. Navigate to Servers

  2. Click Create Server

    • Button in top-right corner

  3. Configure Basic Info

    Name: My Research Server
    Description: Tools for web research and analysis

  4. Select Custom Tools

    • Search for tools you've created
    • Click to add multiple tools
    • Minimum: 1 tool required

  5. Generate API Key (Optional)

    • Enable "Auto-generate API Key"
    • Name it (e.g., "Development Key")
    • Or skip and add keys later

  6. Create

    • Click "Create Server"
    • Server is immediately active

Via API​

See Servers API Reference for programmatic creation.

Server Configuration​

Name & Description​

Choose clear, descriptive names:

✅ Good:

  • "Research & Analysis Tools"
  • "Productivity Suite"
  • "Data Engineering Server"

❌ Bad:

  • "Server 1"
  • "Test"
  • "My Server"

Tool Selection​

Select custom tools that work well together:

Good groupings:

  • Web Research: Google Search + Firecrawl + Perplexity
  • Productivity: Notion + Jira + Gmail
  • Data: Supabase + PostgreSQL + Web Scraper

Avoid:

  • Too many tools (>15) - hard to manage
  • Unrelated tools - confusing for AI
  • Duplicate functionality - wasteful

Managing Servers​

View Server Details​

  1. Servers → Click server name
  2. See:
    • Selected tools
    • API keys
    • Usage statistics
    • MCP configuration

Update Server​

  1. Server page → Click "Edit"
  2. Change:
    • Name/description
    • Add/remove tools
  3. Save changes
  4. Restart IDEs to see updates

Delete Server​

  1. Server page → "Settings" tab
  2. Click "Delete Server"
  3. Confirm deletion
  4. ⚠️ This cannot be undone
  5. All API keys are revoked

API Keys​

See API Keys Guide for detailed key management.

Generate Key​

  1. Server page → "API Keys" tab
  2. Click "Generate Key"
  3. Name it descriptively
  4. Copy immediately (shown once)
  5. Store securely

Types of Keys​

Server-Specific:

  • Tied to one server
  • Created per-server
  • Best for production

Global Keys:

  • Access multiple servers
  • Created in API Keys page
  • Link to servers as needed

Testing Servers​

In Chat​

  1. Navigate to Chat
  2. Select your server
  3. Ask questions that use your tools
  4. Verify responses are correct

In Playground​

  1. Server page → "Playground" tab
  2. Test individual tools
  3. Check parameters and responses
  4. Debug issues

Best Practices​

Security​

  • ✅ Rotate API keys every 90 days
  • ✅ Use server-specific keys in production
  • ✅ Never commit keys to version control
  • ✅ Revoke unused keys immediately

Organization​

  • ✅ One server per use case
  • ✅ Descriptive names
  • ✅ Regular audits of tool usage
  • ✅ Remove unused tools

Performance​

  • ✅ Keep tool count reasonable (under 15 tools)
  • ✅ Monitor credit usage per server
  • ✅ Test before deploying to IDE
  • ✅ Document server purpose

Common Patterns​

Single-Purpose Servers​

Research Server:

  • Web Search
  • Firecrawl
  • Perplexity
  • Web Scraper

Productivity Server:

  • Notion
  • Jira
  • Gmail
  • Calendar

Multi-Purpose Servers​

Personal Assistant:

  • Mix of all frequently-used tools
  • Optimized for your workflow
  • All-in-one convenience

Environment-Specific​

Development Server:

  • Test tools
  • Development credentials
  • Non-production data

Production Server:

  • Stable tools only
  • Production credentials
  • Monitoring enabled

Troubleshooting​

"Must have at least one tool"​

Problem: Can't create server without tools.

Solution: Create custom tools first, then add to server.

"API key generation failed"​

Problem: Auto-generation doesn't work.

Solution: Create server first, add key manually later.

Changes not reflected in IDE​

Problem: Updated server but IDE shows old tools.

Solution: Restart IDE completely (not just reload).

See Also​