AIsa-public/AIsa-mcp-server

Every AIsa data API as MCP tools, behind one endpoint:
580+ tools across 26 servers — SEO and AI visibility, finance, social, web
search, sales and agent mail — reached through five meta tools, so the
catalogue never has to land in a context window. Streamable HTTP. OAuth, with
nothing to paste.
This repository holds @aisa-one/mcp, a small stdio bridge for clients that
cannot speak remote MCP yet. **Most clients do not need it** — give them the URL
above and stop reading at Connecting.
---
Five tools, not hundreds
A client that lists 580 tools has spent its context before the first question.
The root lists five:
| Tool | What it does | Cost |
| --- | --- | --- |
| search | Describe the task in plain words. Returns candidate operations with operation_id, input_schema, price, and sometimes a plan. | Free |
| list_categories | The categories a search can be narrowed to. | Free |
| get_details | One operation's full contract: arguments, response shape, whether it is read-only, price for your account, known pitfalls. | Free |
| use | Run one operation. max_price_usd refuses anything above your cap before it charges. | Per call |
| batch_use | Up to 20 operations at once, under the same cap. | Per call |
Searching and reading schemas costs nothing, so an agent can survey the whole
catalogue before spending anything.
Connecting
One URL, transport streamable-http:
Cursor, VS Code, Windsurf and the rest take the same URL as a url entry in
their MCP settings:
Authorization is OAuth and needs no account to exist first. An unauthenticated
call answers 401 with a WWW-Authenticate header naming
https://mcp.aisa.one/.well-known/oauth-protected-resource/mcp (RFC 9728), and
the authorization server it points to accepts an unregistered client (RFC 7591)
— so the client registers itself, opens a browser, and you click Allow once.
That 401 is the discovery mechanism, not a failure.
Already have a key from console.aisa.one? Send it as
Authorization: Bearer $AISA_API_KEY and no browser opens. That is the way in
over SSH or in CI.
Clients that only speak stdio
Claude Desktop and a few others spawn a local command and talk over stdin and
stdout. This package is that command:
It bridges stdio to the remote endpoint, runs the OAuth browser flow on first
use and caches the token. The bridging itself is
mcp-remote's; this package supplies
the endpoint, the header form and the transport flag so you do not have to.
AISA_API_KEY is picked up from the environment when it is set. Any further
arguments are passed to mcp-remote unchanged.
Pinning a category
Every path below is the same root pinned to a different slice, so each still
carries the five meta tools, the price cap and search over everything. Pinning
changes what tools/list returns, never what is reachable.
| Endpoint | Listed | Reachable | Providers |
| --- | --- | --- | --- |
| https://mcp.aisa.one/mcp | 5 meta tools | everything | 26 |
| https://mcp.aisa.one/gtm/mcp | 43 | 163 | Apollo, Similarweb, X, Instagram, Reddit, Pinterest, YouTube, creator discovery |