Connecting to Seed
Learn how to connect your AI agents (Claude Desktop, Claude Code, or custom MCP clients) to your Seed MCP server.
Overview
Seed is an MCP (Model Context Protocol) server that provides authenticated access to tools, prompts, and resources. To use Seed, you need to:
- Have access to a running Seed server (ask your administrator for the server URL)
- Configure your MCP client to connect to Seed
- Authenticate with your organization's identity provider
Quick Start
Choose your client:
- Claude Desktop - Connect Claude Desktop app to Seed
- Claude Code - Connect Claude Code (VSCode extension) to Seed
- Custom Clients - Connect your own MCP client
What You'll Need
Before connecting, gather this information from your administrator:
| Information | Example | Where to Get It |
|---|---|---|
| Server URL | https://mcp.example.com | From your admin |
| Authorization URL | https://mcp.example.com/oauth/authorize | From your admin |
| Token URL | https://mcp.example.com/oauth/token | From your admin |
| Client ID | seed-abc123xyz | Provided after registration |
| Redirect URI | http://localhost:3000/callback | Depends on your client |
Connection Flow
Connecting to Seed involves:
1. Configure MCP client with server URL
2. Client initiates OAuth flow
3. Browser opens to identity provider
4. You log in and grant consent
5. Client receives access token
6. Client connects to MCP endpoints with token
7. You can now use tools, prompts, and resourcesNext Steps
Choose your client type to get detailed connection instructions:
For Claude Users
- Connecting Claude Desktop - Step-by-step guide for Claude Desktop app
- Connecting Claude Code - Step-by-step guide for VSCode extension
For Developers
- Custom MCP Clients - Integrate Seed with your own MCP client
- API Reference - Complete API documentation
- Authentication Flow - Understand the auth process
Troubleshooting
Common Issues
"Connection refused" or "Cannot connect to server"
- Verify the server URL is correct
- Check the server is running (ask your admin)
- Ensure you can reach the server (network/firewall)
"Authentication failed" or "Invalid token"
- Re-authenticate through the OAuth flow
- Check you're using the correct identity provider
- Verify your account has access
"Tool not found" or "Prompt not available"
- The server administrator controls which tools/prompts are available
- Ask your admin about available features
- Check you're authenticated (some features require auth)
Getting Help
- Having trouble? Check Troubleshooting for common connection issues
- Have questions? See FAQ for frequently asked questions
- Check server status: Ask your administrator or visit your server's
/healthendpoint - View available features: Browse Tools, Prompts, and Resources
- Report issues: Contact your server administrator
What's Next?
Once successfully connected, here's your learning path:
- Tools Overview - Start here! Learn about available tools and try basic commands like "Check the server health"
- Prompts Overview - Explore reusable prompt templates for common tasks
- Resources Overview - Access configuration data and user profiles
- Experiment - Try combining tools, prompts, and resources in your conversations with Claude
Need ideas? Try these example requests:
- "Check the server health and show me the output"
- "Use the greeting prompt with a formal style and my name"
- "Show me my user profile information"
For Administrators
Setting up a Seed server for your organization? Follow this path:
- Installation Guide - Get Seed running (Docker, Docker Compose, or source)
- Configuration Guide - Set up OIDC/OAuth and environment variables
- Deployment Guide - Deploy to production with authentication
- Production Operations - Security, monitoring, and troubleshooting
- Development Guide - Extend with custom tools, prompts, and resources