> ## Documentation Index
> Fetch the complete documentation index at: https://docs.requesty.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP Server Management

> Register, configure, and manage MCP servers for your organization

# MCP Server Management

<Info>
  Manage all your Model Context Protocol (MCP) servers from a centralized dashboard. Register new servers, explore available tools, and configure authentication settings.

  <Note>
    **[Manage MCP servers](https://app.requesty.ai/mcp-gateway)** in the Requesty Console.
  </Note>
</Info>

## Overview

The MCP Server Management interface allows administrators to:

* **Register MCP Servers**: Add new MCP servers with custom configurations
* **Explore Tools**: Discover and preview available tools before enabling them
* **Configure Authentication**: Set up organization-wide or user-specific authentication
* **Manage Tool Access**: Control which tools are available to your team

## Registering MCP Servers

### Using Templates

Choose from pre-configured templates for popular services:

<CardGroup cols={2}>
  <Card title="GitHub" icon="github">
    Repository management, code search, and pull requests
  </Card>

  <Card title="Notion" icon="book">
    Workspace and content management platform
  </Card>

  <Card title="Linear" icon="chart-line">
    Issue tracking and project management
  </Card>

  <Card title="Context7" icon="brain">
    Advanced AI context and knowledge management
  </Card>
</CardGroup>

### Custom Server Configuration

For custom MCP servers, provide:

<Steps>
  <Step title="Basic Information">
    * **Server Name**: Unique identifier within your organization
    * **Server URL**: The MCP endpoint URL
    * **Protocol Type**: `streamable-http` or `sse`
  </Step>

  <Step title="Authentication Headers">
    Configure required authentication headers like `Authorization`, `X-API-Key`, etc.
  </Step>

  <Step title="Explore Tools">
    Test the connection and discover available tools
  </Step>

  <Step title="Select Tools">
    Choose which tools to make available to your team
  </Step>
</Steps>

## Tool Exploration

### Discovery Process

1. **Connect to Server**: Test authentication and connectivity
2. **Fetch Tool List**: Retrieve all available tools from the MCP server
3. **Review Capabilities**: Examine tool descriptions and input schemas
4. **Security Assessment**: Review tool permissions and access requirements

### Tool Information

For each discovered tool, you'll see:

* **Name**: Tool identifier used by AI assistants
* **Description**: Human-readable explanation of functionality
* **Input Schema**: Required parameters and data types
* **Permissions**: What the tool can access or modify

<Warning>
  **Security Note**: Carefully review tool permissions before enabling them. Some tools may have broad access to external systems or sensitive data.
</Warning>

## Server Status Monitoring

### Health Checks

The system continuously monitors:

* **Connectivity**: Server availability and response times
* **Authentication**: Validity of configured credentials
* **Tool Availability**: Changes to available tools
* **Error Rates**: Failed requests and common issues

### Status Indicators

| Status   | Indicator | Description                                 |
| -------- | --------- | ------------------------------------------- |
| Healthy  | 🟢        | Server responding normally                  |
| Warning  | 🟡        | Minor issues or degraded performance        |
| Error    | 🔴        | Server unreachable or authentication failed |
| Disabled | ⚫         | Server manually disabled by admin           |

## Authentication Configuration

### Organization-Wide Keys (Standard & Enterprise)

Set authentication credentials that apply to all users:

```json theme={"dark"}
{
  "headers": {
    "Authorization": "Bearer org-api-key-12345",
    "X-Custom-Header": "organization-value"
  }
}
```

### Per-User Keys (Enterprise Only)

Allow users to provide their own authentication:

* **Required Headers**: Define which headers users must provide
* **Optional Headers**: Headers users can optionally configure
* **Validation**: Automatic testing of user-provided credentials

## Template Library

### Available Templates

<AccordionGroup>
  <Accordion title="GitHub MCP Server" icon="github">
    * **URL**: `https://api.githubcopilot.com/mcp/`
    * **Required Auth**: GitHub Personal Access Token
    * **Tools**: Repository access, code search, issue management, PR operations
    * **Use Cases**: Code review, repository analysis, automated issue creation
  </Accordion>

  <Accordion title="Notion MCP Server" icon="book">
    * **URL**: `https://mcp.notion.com/mcp`
    * **Required Auth**: Notion Integration Token
    * **Tools**: Page creation, database queries, content search, workspace management
    * **Use Cases**: Documentation management, knowledge base queries, content creation
  </Accordion>

  <Accordion title="Linear MCP Server" icon="chart-line">
    * **URL**: `https://mcp.linear.app/sse`
    * **Required Auth**: Linear API Key
    * **Tools**: Issue creation, project tracking, team management, workflow automation
    * **Use Cases**: Bug tracking, feature requests, project coordination
  </Accordion>

  <Accordion title="Asana MCP Server" icon="tasks">
    * **URL**: `https://mcp.asana.com/sse`
    * **Required Auth**: Asana Personal Access Token
    * **Tools**: Task management, project creation, team collaboration, timeline tracking
    * **Use Cases**: Project planning, task assignment, progress tracking
  </Accordion>
</AccordionGroup>

## Best Practices

### Server Selection

<Steps>
  <Step title="Assess Need">
    Determine what external tools your team actually needs
  </Step>

  <Step title="Security Review">
    Evaluate the security implications of each server
  </Step>

  <Step title="Start Small">
    Begin with one or two servers and expand gradually
  </Step>

  <Step title="Monitor Usage">
    Track which tools are actually being used
  </Step>
</Steps>

### Configuration Management

* **Version Control**: Document server configurations for reproducibility
* **Environment Separation**: Use different configurations for dev/staging/prod
* **Regular Audits**: Review enabled servers and tools quarterly
* **Access Logs**: Monitor which users access which tools

### Security Guidelines

* **Principle of Least Privilege**: Only enable necessary tools
* **Credential Rotation**: Regularly update authentication credentials
* **Monitoring**: Set up alerts for unusual access patterns
* **Documentation**: Maintain clear records of what each server accesses

## Troubleshooting

### Common Issues

<AccordionGroup>
  <Accordion title="Connection Failed">
    **Symptoms**: Cannot reach MCP server during exploration

    **Solutions**:

    * Verify the server URL is correct and accessible
    * Check if the server requires specific headers or authentication
    * Test connectivity from your network
    * Contact the MCP server administrator
  </Accordion>

  <Accordion title="Authentication Errors">
    **Symptoms**: 401 or 403 errors during tool exploration

    **Solutions**:

    * Verify API keys are valid and not expired
    * Check if the key has required permissions
    * Ensure headers are formatted correctly
    * Test the key directly with the service's API
  </Accordion>

  <Accordion title="No Tools Found">
    **Symptoms**: Server connects but no tools are discovered

    **Solutions**:

    * Confirm the server implements MCP protocol correctly
    * Check if tools require additional authentication
    * Verify the server's tool list endpoint is working
    * Review server documentation for setup requirements
  </Accordion>
</AccordionGroup>

***

<Card title="Next Steps" icon="arrow-right">
  Once you've registered your MCP servers, learn about [User Key Management](/features/mcp-user-keys) for enterprise authentication or explore [MCP Analytics](/features/mcp-analytics) to monitor usage.
</Card>