Creating Servers
Learn how to create and manage MCP servers in Reeva.
What is a Server?
A server is a collection of tools exposed through the MCP protocol. Each server:
- Has a unique ID and URL used to interact with the server
- Contains contains one or more tools
- Can be accessed via API keys
Creating Your First Server
Via Dashboard
-
Navigate to Servers
- Log into Reeva Dashboard
- Click "Servers" in the sidebar
-
Click Create Server
-
Configure Basic Info
Name: My Research Server
Description: Tools for web research and analysis -
Select Tools
- Search for tools you've created
- Click to add multiple tools
- Minimum: 1 tool required
-
API Keys
- You have three options on this step:
- Auto-generate a new API key and link it to the server
- Link a previously-created key to this new server
- Skip key generation (you will not be able to access the server until a key is generated)
- You have three options on this step:
-
Create
- Click "Create Server"
- Server is immediately active
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 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
- Servers → Click server name
- From this view you'll have access to the following:
- Name and description
- Tools on the the server
- API keys linked to the server
- The URL and auth info to connect to the server
Update Server
- Server page → Click "Edit"
- Change:
- Name/description
- Add/remove tools
- Add/remove AI keys
- Save changes
Delete Server
- Server page → "Settings" tab
- Click "Delete Server"
- Confirm deletion
- ⚠️ This cannot be undone
- All API keys will be unlinked from the server
API Keys
See API Keys Guide for detailed key management.
Generate or Link API Key
- Navigate to Server details page
- Click "Create Key" or "Attach Keys"
- Name it descriptively
- Copy immediately (keys are never shown more than once)
- Store securely
Testing Servers
In Chat
- Navigate to Chat
- Select your server
- Ask questions that use your tools
- Verify responses are correct
In Playground
- Server page → "Playground" tab
- Test individual tools
- Check parameters and responses
- Debug issues
Best Practices
Security
- ✅ Rotate API keys every 90 days
- ✅ Keep sharing keys between servers to a minimum
- ✅ Never commit keys to version control
- ✅ Revoke unused keys immediately
Organization
- ✅ Make server names and descriptions overly verbose and descriptive. Agents interacting with your server will perform much better if you can reduce ambiguity.
- ✅ Avoid adding too many tools to a single server. Servers with large amounts of tools will cause your AI Agents to run slower and will increase the likelihood that they select the wrong tool for assigned tasks.
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 tools first, then add to server.
"API key generation failed"
Problem: Auto-generation doesn't work.
Solution: Create server first, add key manually later.