1. Open VS Code Command Palette: Cmd+Shift+P (Mac) or Ctrl+Shift+P (Windows/Linux)
2. Type and select: MCP: Add Server
3. Choose Server Type: HTTP
4. Enter Server URL: https://devnet.cisco.com/v1/foundation-search-mcp/mcp
5. Set Server ID: devnet-content-search
6. Restart VS Code to activate the server

1. Open Cursor Settings: Cmd+Shift+P (Mac) or Ctrl+Shift+P (Windows/Linux)
2. Navigate to MCP Tools: In the settings menu, find and select Tools & MCP
3. Click Add Custom MCP and configure:

   {
     "mcpServers": {
       "devnet-content-search": {
         "url": "https://devnet.cisco.com/v1/foundation-search-mcp/mcp"
       }
     }
   }

1. Open your Claude Desktop configuration file:
   • Mac: ~/Library/Application Support/Claude/claude_desktop_config.json
   • Windows: %APPDATA%\Claude\claude_desktop_config.json
2. Add the following entry to the mcpServers section:

   {
     "mcpServers": {
       "devnet-content-search": {
         "command": "npx",
         "args": [
           "mcp-remote@latest",
           "https://devnet.cisco.com/v1/foundation-search-mcp/mcp"
         ]
       }
     }
   }

3. Save the file and restart Claude Desktop
4. The DevNet Content Search tool will now be available in your Claude conversations

1. Add the MCP server to your Claude Code configuration by running:

   claude mcp add devnet-content-search --transport http https://devnet.cisco.com/v1/foundation-search-mcp/mcp

2. Verify the server was added successfully:

   claude mcp list

3. The DevNet Content Search tools will now be available in your Claude Code sessions

1. Open your LibreChat configuration file librechat.yaml in the root of your LibreChat installation
2. Add the following under the mcpServers section:

   mcpServers:
     devnet-content-search:
       type: http
       url: https://devnet.cisco.com/v1/foundation-search-mcp/mcp

3. Save the file and restart your LibreChat instance
4. The DevNet Content Search tools will be available to agents and assistants configured in LibreChat

1. Open Settings (Cmd+, on Mac or Ctrl+Alt+S on Windows/Linux)
2. Navigate to Tools → AI Assistant → Model Context Protocol (MCP)
3. Click the + button to add a new server and configure:

   {
     "mcpServers": {
       "devnet-content-search": {
         "command": "npx",
         "args": [
           "mcp-remote@latest",
           "https://devnet.cisco.com/v1/foundation-search-mcp/mcp"
         ]
       }
     }
   }

4. Click Apply → OK and restart your IDE
5. The DevNet Content Search tools will now be available in the AI Assistant chat panel

Search comprehensive Meraki API documentation covering network infrastructure management, security policies, wireless configuration, and monitoring capabilities.

Parameters:

• keyword (required): Search terms for finding relevant documentation
• return_api_only (optional): Set to true for API specs only, false for complete documentation context
• top_k (optional): Number of results to return (default: 3, max: 10)

Use Cases:

• Finding API endpoints for specific network operations
• Understanding authentication and authorization methods
• Exploring webhook and event handling capabilities
• Discovering monitoring and analytics APIs

Response Structure:
All responses include structured data with these key fields:

Core Information:

• name: Document or API endpoint title
• description: Brief summary of functionality
• content: Full text content when applicable

Metadata:

• products: Associated Cisco product lines
• tags: Searchable keywords and categories
• categories: Primary classification (e.g., "Networking", "Security")

API-Specific Fields:

• api_path: RESTful endpoint URL pattern
• api_method: HTTP verb (GET, POST, PUT, DELETE)
• api_operation_id: Unique OpenAPI operation identifier
• openapi_specification: Complete API specification (JSON string)
• documentation_url: Direct link to official documentation

Sample Response:

{
  "jsonrpc": "2.0",
  "id": 1,
  "result": {
    "content": [
      {
        "type": "text", 
        "text": "Found 2 results for Meraki authentication APIs:\n\n1. Create Network Meraki Auth User\n2. OAuth 2.0 Authentication Overview"
      }
    ],
    "structuredContent": {
      "result": [
        {
          "name": "Create Network Meraki Auth User",
          "description": "Authorize a user configured with Meraki Authentication for a network",
          "products": ["Meraki"],
          "tags": ["networks", "configure", "merakiAuthUsers"],
          "categories": ["Networking"],
          "api_path": "/networks/{networkId}/merakiAuthUsers",
          "api_method": "post", 
          "api_operation_id": "createNetworkMerakiAuthUser",
          "openapi_specification": "{\"description\": \"Authorize a user...\", \"operationId\": \"createNetworkMerakiAuthUser\", \"parameters\": [...], \"requestBody\": {...}, \"responses\": {...}}",
          "documentation_url": "https://developer.cisco.com/meraki/api-v1/create-network-meraki-auth-user"
        }
      ]
    },
    "isError": false
  }
}

Access Catalyst Center API documentation for enterprise network management, automation workflows, and infrastructure orchestration.

Parameters:

• keyword (required): Search terms for relevant documentation
• return_api_only (optional): Filter for API specifications vs. general documentation
• top_k (optional): Maximum results to return

Use Cases:

• Network device management and configuration
• Policy and compliance automation
• Performance monitoring and analytics
• Troubleshooting and diagnostic tools

Retrieve specific API endpoint details using exact operation identifiers for precise documentation lookup.

Parameters:

• operation_id (required): The exact OpenAPI operation ID (e.g., createNetworkMerakiAuthUser)

Use Cases:

• Getting complete specifications for known API operations
• Validating parameter requirements and response formats
• Finding related endpoints and dependencies

When Your AI Assistant Isn't Finding DevNet Content

If your assistant responds with generic networking advice instead of specific Cisco API documentation, try these approaches:

🎯 Making Your Requests More Specific

Instead of: "How do I configure a firewall?"
Try: "Show me the Meraki L3 firewall API endpoints for configuring traffic rules"

Instead of: "I need network monitoring tools"
Try: "Find Catalyst Center APIs for collecting device performance metrics"

🔍 Framing Your Questions for DevNet Search

Technology-Specific + Action-Oriented:

• "Find Meraki L3 firewall API endpoints for configuring traffic rules"
• "Show me Catalyst Center APIs for network device inventory management"
• "I need the OpenAPI specification for Meraki wireless SSID configuration"

Current Documentation Requests:

• "What are the current Catalyst Center APIs for compliance reporting?"
• "Find the latest Meraki Dashboard APIs for switch port management"
• "Get current DevNet documentation for OAuth 2.0 authentication"

Problem-Solution Approach:

• "I'm building network automation - find relevant Catalyst Center APIs"
• "My monitoring dashboard needs Meraki device status data - what APIs exist?"
• "Help me integrate Catalyst Center with my ITSM system"

⚙️ IDE Assistant Configuration Tips

Some development environments allow you to customize AI assistant behavior. Configure your IDE with specific instructions to ensure reliable tool usage:

VS Code/Cursor Custom Instructions:

For Cisco networking questions, always search official DevNet documentation first.
Use the available MCP tools for current API specifications rather than 
providing general networking advice. Focus on specific Cisco platforms:
Meraki Dashboard, Catalyst Center, and DevNet resources.

Avoid Generic Terms That May Not Trigger Tools:

• ❌ "networking tools" → ✅ "Meraki network management APIs"
• ❌ "device configuration" → ✅ "Catalyst Center device provisioning endpoints"
• ❌ "monitoring solutions" → ✅ "DevNet network analytics API specifications"

Common Issues and Solutions

Getting Help

If you encounter issues or need assistance:

1. Check that your MCP client is properly configured
2. Verify your search queries follow the expected format
3. Contact the DevNet team for service-related issues