What can you do with this server?

The MCP360 Universal Gateway is a unified MCP server that enables AI agents to discover and execute 100+ external tools and services through two meta-tools: Core Capabilities: * Search for tools across all connected MCP servers using keywords or tool names, with optional result limits to discover available tools, their descriptions, and required parameters * Execute any tool by specifying the service, tool name, and parameters (as object or string) Access to Services: * 🔍 Keyword research and SEO analysis * ✉️ Email verification and validation * 🕷️ Web scraping and content extraction * 📈 Google Trends data * 💰 Cryptocurrency prices and market data * 📊 OnPage SEO checking * Custom MCP servers from your MCP360 account Key Features: * Enterprise-grade security with API key authentication * Universal compatibility with Claude Desktop, Cursor, Windsurf, VS Code (Cline), and other MCP-compatible platforms * Flexible deployment supporting custom gateway URLs and environment variables for enterprise configurations * Performance optimized with global CDN delivery and optional global installation

Which integrations are available for this server?

Provides access to real-time cryptocurrency prices and market data for Bitcoin and other cryptocurrencies. Provides community support through Discord for the MCP360 platform. Enables access to Google Trends data for search trends and interest metrics.

How do I use MCP360 Universal Gateway?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@MCP360 Universal Gateway search for tools that can help me analyze website SEO" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

MCP360 Universal Gateway

Official

by mcp360

Overview Schema Related Servers Score Discussions

TypeScript

Remote

🚀 MCP360 Universal Gateway

License: MIT Node.js Version

Get Started • Features • Documentation • Support

🎯 What is MCP360?

MCP360 is a unified MCP gateway that gives AI agents access to 100+ external tools, including prebuilt MCPs and custom MCP servers. You can connect your agents once and immediately run searches, research tasks, SEO workflows, and other operational actions. Instead of spending days integrating multiple APIs, connect to 100+ tools easily with a simple setup, or add your own Custom MCPs when you need specific logic or data.

Related MCP server: Nervora

✨ Key Features

🚀 Quick Start

Step 1: Get Your API Key

Sign up at mcp360.ai 🎉
Navigate to Settings → API Keys ⚙️
Click Generate New Key 🔑
Copy your API key securely 📋

Step 2: Choose Your Platform

Configuration File Locations:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json

Add this configuration:

{
  "mcpServers": {
    "mcp360": {
      "command": "npx",
      "args": ["-y", "@mcp360/universal-gateway"],
      "env": {
        "MCP360_API_KEY": "your_api_key_here"
      }
    }
  }
}

Restart Claude Desktop and you're ready! 🎊

Open Cursor Settings: Cmd/Ctrl + Shift + J
Navigate to the MCP section
Add server configuration:

{
  "mcpServers": {
    "mcp360": {
      "command": "npx",
      "args": ["-y", "@mcp360/universal-gateway"],
      "env": {
        "MCP360_API_KEY": "your_api_key_here"
      }
    }
  }
}

Restart Cursor to activate! 🚀

Configuration File Locations:

macOS/Linux: ~/.config/claude-code/mcp_settings.json
Windows: %APPDATA%\claude-code\mcp_settings.json

Add this configuration:

{
  "mcpServers": {
    "mcp360": {
      "command": "npx",
      "args": ["-y", "@mcp360/universal-gateway"],
      "env": {
        "MCP360_API_KEY": "your_api_key_here"
      }
    }
  }
}

Restart Claude Code to load the gateway! ✨

Configuration File Locations:

macOS: ~/Library/Application Support/Windsurf/mcp_config.json
Windows: %APPDATA%\Windsurf\mcp_config.json

Add this configuration:

{
  "mcpServers": {
    "mcp360": {
      "command": "npx",
      "args": ["-y", "@mcp360/universal-gateway"],
      "env": {
        "MCP360_API_KEY": "your_api_key_here"
      }
    }
  }
}

Restart Windsurf to activate! 🌟

Install the Cline extension
Open Cline settings
Add MCP server configuration:

{
  "mcpServers": {
    "mcp360": {
      "command": "npx",
      "args": ["-y", "@mcp360/universal-gateway"],
      "env": {
        "MCP360_API_KEY": "your_api_key_here"
      }
    }
  }
}

Reload VS Code to activate the gateway! 💡

Go to your YourGPT Dashboard
Select Functions from the sidebar
Choose the MCP Server option
You'll see two options:
- Browse Marketplace MCP - Select from pre-configured MCP servers
- Add Custom MCP - Add your own MCP server configuration

Use MCP360 in YourGPT:

Select Add MCP
Enter the server details:
- Name: mcp360
- URL: https://connect.mcp360.ai/v1/mcp360/mcp?token=YOUR_API_KEY

Save and activate to start using MCP360 in YourGPT! 🎉

OpenClaw is an open-source, self-hosted agent runtime that treats AI agents as long-lived managed processes with state, health, tooling, and execution boundaries. MCP360 connects to OpenClaw as a unified tool gateway.

Step 1: Install OpenClaw globally

npm i -g openclaw

openclaw --version

Step 2: Run initial configuration

openclaw configure

Step 3: Start the gateway and verify health

openclaw gateway

openclaw gateway status

openclaw doctor

All health checks must pass before proceeding.

Step 4: Install MCP tooling for inspection

npm i -g mcporter

mcporter --version

Step 5: Create a stable MCP configuration directory

mkdir -p ~/mcp

cd ~/mcp

Step 6: Register MCP360 as an MCP server

mcporter config add mcp360 \
--command 'npx mcp-remote "https://connect.mcp360.ai/v1/mcp360/mcp?token=YOUR_API_KEY"'

Step 7: Confirm registration and verify tool access

mcporter config list

mcporter list

If mcporter list returns structured tool definitions, your MCP360 connection is working correctly. ✅

Tip: Use openclaw tui to run OpenClaw in the terminal instead of the dashboard.

📖 For a full walkthrough, see the OpenClaw + MCP360 setup guide.

🚄 Pro Tip: Global Installation

For faster startup times, install globally:

npm install -g @mcp360/universal-gateway

Then update your config to use the global command:

{
  "mcpServers": {
    "mcp360": {
      "command": "mcp360-gateway",
      "env": {
        "MCP360_API_KEY": "your_api_key_here"
      }
    }
  }
}

🛠️ Core Tools

The gateway provides 2 powerful meta-tools that unlock access to 100+ services:

1️⃣ `search` - Discover Available Tools

Find the perfect tool for your task across all connected MCP servers.

Parameters:

query (optional): Search term to filter by name or description

Examples:

💬 "Search for email tools"
💬 "Show me all available tools"
💬 "Find tools for SEO"
💬 "What tools can help with keyword research?"

Returns: Comprehensive list of matching tools with names, descriptions, and parameters.

2️⃣ `execute` - Run Any Tool

Execute any tool from any connected MCP server with dynamic parameters.

Parameters:

tool_name (required): Name of the tool to execute
arguments (optional): Tool-specific parameters as an object

Examples:

💬 "Execute verify_email with email 'test@example.com'"
💬 "Run keyword_research with keyword 'AI tools'"
💬 "Execute get_crypto_price for Bitcoin"

Returns: Tool-specific results tailored to your request.

🌟 Available Services

🏪 MCP360 Marketplace

Service	Description	Use Cases
🔍 Keyword Research	SEO keyword analysis & search volumes	Content strategy, SEO optimization
📊 OnPage SEO Checker	Website SEO element analysis	Site audits, optimization
✉️ Email Verification	Validate email addresses	List cleaning, form validation
🕷️ Web Scraping	Extract content from websites	Data collection, monitoring
📈 Google Trends	Search trends & interest data	Market research, trending topics
💰 Cryptocurrency	Real-time crypto prices & market data	Price tracking, portfolio management

🔧 Your Custom MCPs

All custom MCP servers you've created in your MCP360 account are automatically available through the Universal Gateway!

📖 Typical Workflow

graph LR
    A[🔍 Discover Tools] --> B[📋 Check Parameters]
    B --> C[⚡ Execute Tool]
    C --> D[📊 Get Results]
    D --> E{Need More?}
    E -->|Yes| A
    E -->|No| F[✅ Done]

Example Session

# Step 1: Discover
User: "Search for email tools"
→ Returns: verify_email, send_email, email_lookup, etc.

# Step 2: Check Details
→ See: verify_email requires { email: string }

# Step 3: Execute
User: "Execute verify_email with email 'john@example.com'"
→ Returns: { valid: true, deliverable: true, ... }

How it works:

🔐 Authenticate with your API key
🔄 Aggregate all available tools from marketplace and custom MCPs
🎯 Expose them through 2 simple meta-tools: search and execute
⚡ Execute tools dynamically based on your requests

🔧 Configuration

Environment Variables

Variable	Description	URL
`MCP360_TOOL_URL`	Your MCP360 API key	`https://connect.mcp360.ai/v1/mcp360/_tool_name_/mcp`
`MCP360_UNIVERSAL_GATEWAY`	Custom gateway URL	`https://connect.mcp360.ai/v1/mcp360/mcp`

Custom Gateway URL

For enterprise deployments or custom configurations:

{
  "mcpServers": {
    "mcp360": {
      "command": "npx",
      "args": ["-y", "@mcp360/universal-gateway"],
      "env": {
        "MCP360_API_KEY": "your_api_key_here",
        "MCP360_GATEWAY_URL": "https://your-custom-gateway.com/mcp"
      }
    }
  }
}

🚀 Quick Start

Step 1: Get Your API Key (Optional)

MCP360 supports flexible authentication to get you started quickly:

Sign up at mcp360.ai 🎉
Navigate to Settings → API Keys ⚙️
Click Generate New Key 🔑
Copy your API key and add it to your configuration 📋

No API key? No problem! Simply connect MCP360 without an API key, and our OAuth 2.0 flow will automatically activate:

🌐 Your browser opens to the MCP360 sign-in page
🔓 You grant permission to access your MCP360 account
📂 You select your project and API key
✅ Authentication completes seamlessly

Benefits:

⚡ Zero manual API key management
🔄 Easy project switching
🔒 Secure token-based authentication
🎯 Granular permission control

Note: If you don't provide an API key in your configuration, OAuth 2.0 authentication will trigger automatically on first use.

🔒 Enterprise-Grade Security

🛡️ Security Compliance & Certifications

MCP360 is built with enterprise security at its core, ensuring your data is protected with industry-leading standards.

🔑 Secure Authentication Options

Method	Security Level	Best For
OAuth 2.0	🔒🔒🔒 Highest	Production environments, team access
API Key	🔒🔒 High	Development, personal projects

Security Features:

🔐 Encrypted Communication: All data transmitted over TLS 1.3
🔄 Token Rotation: Automatic OAuth token refresh
📊 Audit Logs: Complete activity tracking
🚫 Rate Limiting: Protection against abuse
🛡️ DDoS Protection: Enterprise-grade infrastructure
🔍 Anomaly Detection: AI-powered security monitoring

📚 Resources

Learn how to set up, test, and manage MCP servers and functions using MCP360:

📖 Additional Learning Resources

💬 Support & Community

📄 License

This project is licensed under the MIT License - see the LICENSE file for details.

🙏 Acknowledgments

Built with ❤️ by the team at MCP360

Special thanks to:

🌟 All our contributors
💡 The Anthropic team for Claude Desktop
🚀 The open-source community

🌟 Star Us on GitHub!

If you find MCP360 Universal Gateway helpful, please consider giving us a star ⭐

GitHub stars

Made with ❤️ by MCP360

Website • Documentation • GitHub • npm

Available Tools

2 tools

executeD

execute tool

ParametersJSON Schema

Name	Required	Description	Default
`service`	Yes
`tool`	Yes
`parameters`	Yes

TDQS

D1.1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full responsibility for behavioral disclosure but provides none. It doesn't indicate whether this is a read or write operation, what permissions are required, what side effects might occur, or any rate limits or constraints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

While technically concise with just two words, this is a case of harmful under-specification rather than effective brevity. The description fails to provide any meaningful information that would help an agent understand or use the tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 3 required parameters, no annotations, no output schema, and 0% schema description coverage, the description is completely inadequate. It provides no information about purpose, behavior, parameters, or expected outcomes, making it impossible for an agent to use this tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 0% description coverage for all 3 parameters (service, tool, parameters), and the description adds absolutely no information about what these parameters mean, their expected formats, or how they should be used together.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'execute tool' is a tautology that merely restates the tool name without specifying what it actually does. It provides no information about the action being performed, the resources involved, or how it differs from its sibling 'search' tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description offers no guidance on when to use this tool versus alternatives. There's no mention of appropriate contexts, prerequisites, or comparisons to the sibling 'search' tool, leaving the agent with no usage direction.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

searchD

search tool

ParametersJSON Schema

Name	Required	Description	Default
`query`	No	The query to search the tools by name or keywords
`limit`	No	The limit of results to return

TDQS

D1.7/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden for behavioral disclosure. 'search tool' reveals nothing about whether this is read-only or destructive, what permissions are needed, how results are returned, pagination behavior, rate limits, or error conditions. It's completely inadequate for a tool with parameters.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

While technically concise with just two words, this is under-specification rather than effective conciseness. The description fails to communicate essential information and doesn't front-load critical details. Every sentence should earn its place, but here the single phrase doesn't earn its place by being informative.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has parameters and no output schema, the description is completely inadequate. It doesn't explain what the tool searches, how results are structured, what happens when no results are found, or any behavioral context. With no annotations and minimal description, this leaves the agent with insufficient information to use the tool effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema fully documents both parameters (query and limit). The description adds zero additional parameter information beyond what's in the schema. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'search tool' is a tautology that merely restates the tool name without specifying what resource is being searched. It doesn't distinguish this search tool from the sibling 'execute' tool, nor does it clarify what domain or context the search operates in (tools, documents, data, etc.).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. There's no mention of the sibling 'execute' tool or any context about appropriate use cases, prerequisites, or limitations. The agent receives zero direction on tool selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

2 tool updatesv1.0.0Dec 10, 2025
- First observedexecute
- First observedsearch

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

C2/5.0

Disambiguation5/5

The two tools have clearly distinct purposes: 'execute' suggests performing an action or running something, while 'search' implies finding or retrieving information. There is no overlap or ambiguity between these functions, making it easy for an agent to choose the correct tool.

Naming Consistency5/5

Both tool names follow a consistent pattern: they are single, descriptive verbs in lowercase. There are no deviations in style or convention, making the naming predictable and easy to understand across the set.

Tool Count2/5

With only two tools, the server feels thin for a 'Universal Gateway', which implies broad functionality. This limited set is likely insufficient for comprehensive coverage of a gateway's typical operations, such as routing, transformation, or monitoring, making it borderline too few for the apparent scope.

Completeness2/5

Given the server's name as a 'Universal Gateway', there are significant gaps in the tool surface. Core gateway operations like configuration management, logging, or connection handling are missing, leaving agents unable to perform essential tasks beyond basic execution and search, which will likely cause failures in broader workflows.

Maintenance

ActivityInactive

ResponsivenessSyncing

Resources

Need Help?

Reddit Discussion

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

enterprise-mcp-gateway B
com.thenextgennexus
Unified gateway exposing 150+ tools across all NexGenData MCP servers via one endpoint.
Developer Tools API Testing
1522
Danube AIOAuth
com.danubeai
Marketplace gateway: 100+ services and 1,400+ tools behind one MCP connection with unified auth
Developer Tools App Automation
1
OneOAuth
ai.withone
Search, document and execute authenticated API calls across 700+ apps via one MCP server
API Testing App Automation
110
Algenta MCP Server C
io.github.thyn-ai
Governed data discovery, exact queries, decisions, simulations, and runtime utilities over MCP.
Data Platforms Search RAG Systems
1402

Related MCP Servers

MCP Research Router
Agent Orchestration Autonomous Agents
SpiritHerb
A
license
A
quality
C
maintenance
Aggregates and routes multiple MCP servers with intelligent tool recommendation and batch parallel execution, enabling unified access and efficient tool usage.
Updated 7 months ago (2026-01-27 00:57 UTC)
2
16
4
MIT
Nervora
Security Agent Orchestration
sveselaj
A
license
Not graded
quality
C
maintenance
A secure MCP gateway for enterprise AI tool execution, enabling governed invocation of business tools with authentication, RBAC, audit logging, PII redaction, and async processing.
Updated 2 months ago (2026-06-30 06:17 UTC)
Apache 2.0
OpenXNet MCP Server
AI & Machine Learning Data Platforms Observability
synapxnet
A
license
Not graded
quality
B
maintenance
Provides an isolated MCP gateway for SynapXnet AIOps, DataOps, and MLOps evidence-to-remediation workflows, with OAuth validation, scoped tool discovery, persistent approvals, and audit tracking.
Updated 20 days ago (2026-08-18 06:37 UTC)
AGPL 3.0
One Agent Pluginofficial
App Automation
withoneai
A
license
Not graded
quality
C
maintenance
Provides a remote MCP server with four tools to list, search, and execute actions across 500+ integrated apps, using OAuth and platform-specific knowledge packages to guide agents.
Updated 18 days ago (2026-08-20 14:41 UTC)
1
MIT

Appeared in Searches

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mcp360/unified-gateway-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server

🚀 MCP360 Universal Gateway

🎯 What is MCP360?

✨ Key Features

🚀 Quick Start

Step 1: Get Your API Key

Step 2: Choose Your Platform

🚄 Pro Tip: Global Installation

🛠️ Core Tools

1️⃣ search - Discover Available Tools

2️⃣ execute - Run Any Tool

🌟 Available Services

🏪 MCP360 Marketplace

🔧 Your Custom MCPs

📖 Typical Workflow

Example Session

🔧 Configuration

Environment Variables

Custom Gateway URL

🚀 Quick Start

Step 1: Get Your API Key (Optional)

🔒 Enterprise-Grade Security

🛡️ Security Compliance & Certifications

🔑 Secure Authentication Options

📚 Resources

📖 Additional Learning Resources

💬 Support & Community

📄 License

🙏 Acknowledgments

🌟 Star Us on GitHub!

Available Tools

TDQS

TDQS

Tool Schema Changelog

TDQS

Maintenance

Resources

Looking for Admin?

Related MCP Connectors

Related MCP Servers

MCP Research Router

Nervora

OpenXNet MCP Server

One Agent Pluginofficial

Appeared in Searches

Latest Blog Posts

MCP directory API

1️⃣ `search` - Discover Available Tools

2️⃣ `execute` - Run Any Tool