Skip to main content

Custom MCP Servers

Add any MCP-compatible server to Oodle to extend the AI Assistant's capabilities with additional tools, resources, and context. This allows you to connect proprietary systems, internal tools, or third-party services that support the Model Context Protocol.

What are Custom MCP Servers?​

Custom MCP servers let you connect any service that implements the Model Context Protocol to Oodle. When connected, the AI Assistant gains access to the tools and resources provided by that server.

Use cases include:

  • Internal tools: Connect company-specific tools and APIs
  • Third-party services: Integrate with external platforms
  • Custom automation: Add specialized debugging or analysis tools
  • Data sources: Give the AI access to additional context

Prerequisites​

  • An MCP-compatible server with an HTTP endpoint
  • The server URL and any required authentication headers
  • An active Oodle instance

Adding a Custom MCP Server​

Step 1: Open the Integration​

  1. Log in to your Oodle instance
  2. Navigate to Settings → Integrations
  3. Find the External MCP Servers integration card
  4. Click to open the configuration drawer

Step 2: Add a New Server​

  1. Click Add MCP Server
  2. Fill in the server details:
    • Name: A descriptive name for the server
    • URL: The HTTP endpoint of the MCP server
    • Description (optional): What the server provides
    • Headers (optional): Authentication headers (e.g., API keys)
    • Additional Metadata (optional): Context for the AI about when to use this server
  3. Click Save

Step 3: Verify the Connection​

After saving, Oodle automatically tests the connection and displays:

  • Tools: Number of tools available from the server
  • Status: Whether the server is reachable and responding

Configuration Options​

Server URL​

The HTTP endpoint where your MCP server is running. Must be accessible from Oodle's servers.

https://your-mcp-server.example.com/mcp

Authentication Headers​

Add custom headers for authentication. Common patterns:

{
  "Authorization": "Bearer YOUR_API_KEY"
}
{
  "X-API-Key": "YOUR_API_KEY"
}

Additional Metadata​

Provide context to help the AI understand when to use this server:

Use this server for querying the customer database.
Available for production environment issues only.

Managing MCP Servers​

View All Servers​

The External MCP Servers integration shows a table of all configured servers with:

  • Server name and URL
  • Number of available tools
  • Connection status (Enabled/Disabled)

Edit a Server​

  1. Click on a server row in the table
  2. Modify the configuration
  3. Click Save

Test a Server​

  1. Click the three-dot menu on a server row
  2. Select Test
  3. View the connection result and available tools

Delete a Server​

  1. Click the three-dot menu on a server row
  2. Select Delete
  3. Confirm the deletion

Building Your Own MCP Server​

To create a custom MCP server that works with Oodle:

  1. Implement the MCP specification
  2. Expose an HTTP endpoint that handles MCP requests
  3. Define the tools your server provides
  4. Add authentication if needed

Example Server Response​

Your server should respond to tool listing requests with:

{
  "tools": [
    {
      "name": "search_database",
      "description": "Search the customer database",
      "inputSchema": {
        "type": "object",
        "properties": {
          "query": { "type": "string" }
        }
      }
    }
  ]
}

Troubleshooting​

Server shows "Error" status​

  • Verify the URL is correct and accessible
  • Check that authentication headers are properly formatted
  • Ensure the server is running and responding to requests
  • Check server logs for error details

Tools not appearing​

  • Verify the server implements the MCP tools endpoint
  • Check that the server returns valid JSON
  • Ensure tools have proper names and descriptions

Connection timeout​

  • Check network connectivity between Oodle and your server
  • Verify firewalls allow the connection
  • Ensure the server responds within the timeout period

Authentication failures​

  • Verify API keys and tokens are correct
  • Check header names match what the server expects
  • Ensure tokens haven't expired

Security Best Practices​

  • Use HTTPS: Always use encrypted connections
  • Rotate credentials: Regularly update API keys and tokens
  • Limit scope: Only grant the minimum required permissions
  • Monitor access: Review AI interactions with external servers
  • Network security: Use firewalls and IP allowlists where possible

Support​

If you encounter issues with custom MCP servers:

  • Check the troubleshooting section above
  • Verify your MCP server implementation against the specification
  • Contact support through the Oodle UI for assistance