MCP Omni-Tool
<div align="center">
# ๐ฎ MCP Omni-Tool
### Stop installing 50 MCP servers. Install one.
**One MCP server. Thousands of APIs. Zero config headaches.**
[](https://www.npmjs.com/package/mcp-omni-tool)
[](LICENSE)
[](https://modelcontextprotocol.io)
<br />
> Your AI agent shouldn't need 50 different MCP servers to be useful.
> It needs **one** that connects to everything.
<br />
[Get Started โ](#-quick-start) ยท [See Examples โ](#-usage) ยท [Get $5 Free Credit โ](#-5-free-credit-for-new-signups)
</div>
---
## ๐คฏ The Problem
Every new API your agent needs = another MCP server to find, install, configure, and maintain.
Want Slack, GitHub, Stripe, Twilio, and 46 other services? That's 50 `package.json` entries, 50 sets of API keys, 50 things that can break on update.
**There's a better way.**
## โก The Solution
MCP Omni-Tool is a single MCP server powered by [AgentClear](https://agentclear.dev) that gives your AI agent **dynamic access to thousands of APIs** through one install and one API key.
Your agent **discovers** what it needs, then **calls it** โ all through a unified proxy. No per-service config. No dependency hell.
```
โโโโโโโโโโโโโโโ โโโโโโโโโโโโโโโโโโโโ โโโโโโโโโโโโโโโโโโโโโโโโ
โ Your Agent โโโโโโโถโ MCP Omni-Tool โโโโโโโถโ AgentClear Gateway โ
โ (Claude, โ โ (1 MCP server) โ โ โ
โ Cursor, โ โ โ โ Slack โ GitHub โ
โ etc.) โโโโโโโโ โโโโโโโโ Stripe โ Twilio โ
โโโโโโโโโโโโโโโ โโโโโโโโโโโโโโโโโโโโ โ Notion โ Linear โ
โ ... 1000s more โ
โโโโโโโโโโโโโโโโโโโโโโโโ
```
---
## ๐ Quick Start
### 1. Install
```bash
npm install -g mcp-omni-tool
```
### 2. Get Your API Key
Sign up at [agentclear.dev](https://agentclear.dev) and grab your key (starts with `axk_`).
> ๐ **Every new account gets $5 in free credit** โ no card required.
### 3. Configure
Add to your MCP client config (e.g. `claude_desktop_config.json`):
```json
{
"mcpServers": {
"omni-tool": {
"command": "mcp-omni-tool",
"env": {
"AGENTCLEAR_API_KEY": "axk_your_key_here"
}
}
}
}
```
### 4. Go
That's it. Your agent now has access to thousands of APIs.
---
## ๐ Usage
MCP Omni-Tool exposes two core operations to your agent:
### `discover` โ Find Available APIs
Your agent calls `discover` to search for services matching what it needs.
```json
POST https://agentclear.dev/api/discover
{
"query": "send a Slack message",
"api_key": "axk_your_key_here"
}
```
**Response:**
```json
{
"services": [
{
"service_id": "slack_post_message",
"name": "Slack โ Post Message",
"description": "Send a message to a Slack channel or DM",
"parameters": {
"channel": "string (required)",
"text": "string (required)",
"thread_ts": "string (optional)"
}
}
]
}
```
### `proxy` โ Call Any Discovered API
Once discovered, your agent calls the service directly through the proxy:
```json
POST https://agentclear.dev/api/proxy/slack_post_message
{
"api_key": "axk_your_key_here",
"params": {
"channel": "#general",
"text": "Deployed v2.4.1 to production โ
"
}
}
```
**That's the entire pattern.** Discover โ Proxy. Your agent figures out the rest.
---
## ๐ Why Omni-Tool?
| | 50 Individual MCP Servers | 1 MCP Omni-Tool |
|---|---|---|
| **Install** | 50 packages, 50 configs | 1 package, 1 key |
| **API Keys** | Manage 50 separate keys | 1 AgentClear key |
| **Updates** | 50 packages to keep current | 1 package, always current |
| **New APIs** | Find โ install โ configure โ restart | Already there. Just call it. |
| **Agent Complexity** | Must know which server handles what | Discovers capabilities dynamically |
| **Failure Surface** | 50 potential breaking points | 1 stable gateway |
| **Setup Time** | Hours | **2 minutes** |
| **Cost** | $0 + your time ร 50 | **$5 free to start** |
---
## ๐ $5 Free Credit for New Signups
Every new AgentClear account gets **$5 in free credit** โ no credit card required.
That's enough for hundreds of API calls to test integrations, build prototypes, or just see what your agent can actually do when it has access to everything.
**โ [Sign up at agentclear.dev](https://agentclear.dev)**
---
## ๐ฐ Framework Authors & Template Builders: Earn 40% Revenue Share
Building an MCP-powered template, framework, starter kit, or boilerplate?
**Bundle MCP Omni-Tool and earn 40% of the revenue** generated by users who sign up through your referral.
### How it works:
1. Include MCP Omni-Tool in your project's MCP config
2. Register as a referral partner at [agentclear.dev/partners](https://agentclear.dev/partners)
3. Add your referral tag to the config
4. Earn **40% rev-share** on every user who activates through your template
This isn't an afterthought affiliate program โ it's a core part of the model. We want framework authors to win when their users succeed.
**โ [Become a Partner](https://agentclear.dev/partners)**
---
## ๐ง Supported Clients
MCP Omni-Tool works with any MCP-compatible client:
- **Claude Desktop**
- **Cursor**
- **Windsurf**
- **Continue**
- **Custom MCP integrations**
---
## ๐ API Key Format
All AgentClear API keys start with `axk_` followed by a unique token:
```
axk_a1b2c3d4e5f6...
```
Keep your key secure. You can rotate keys at any time from the [AgentClear dashboard](https://agentclear.dev/dashboard).
---
## ๐ License
MIT ยฉ [AgentClear](https://agentclear.dev)
---
<div align="center">
**Built by [AgentClear](https://agentclear.dev)** โ the universal API gateway for AI agents.
[Get Started](https://agentclear.dev) ยท [Documentation](https://agentclear.dev/docs) ยท [Partner Program](https://agentclear.dev/partners)
</div>
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: call invokes a discovered service, discover finds APIs, discover_and_call combines both, and list_services browses the marketplace. No overlap in functionality.
Tool names follow a consistent verb-based pattern (call, discover, list_services). The compound discover_and_call is a minor deviation but still clear and predictable.
With 4 tools, the set is well-scoped for an API discovery and calling service. It covers the essential interactions without unnecessary bloat, though a few more tools (e.g., authentication) could be added without clutter.
The tool surface covers the core workflow: discover APIs, browse services, and call them. The combined discover_and_call streamlines common usage. Minor gaps like account management or call history are reasonable omissions for a focused tool.