Skip to main content
Glama
AIsa MCP

AIsa MCP

Official

AIsa MCP

Every AIsa data API as MCP tools, behind one endpoint:

https://mcp.aisa.one/mcp

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.

Related MCP server: Crawlora MCP

Connecting

One URL, transport streamable-http:

# Claude Code
claude mcp add --transport http -s user aisa https://mcp.aisa.one/mcp

# Codex
codex mcp add aisa --url https://mcp.aisa.one/mcp

Cursor, VS Code, Windsurf and the rest take the same URL as a url entry in their MCP settings:

{
  "mcpServers": {
    "aisa": {
      "type": "streamable_http",
      "url": "https://mcp.aisa.one/mcp"
    }
  }
}

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:

{
  "mcpServers": {
    "aisa": {
      "command": "npx",
      "args": ["-y", "@aisa-one/mcp"]
    }
  }
}

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.

npx -y @aisa-one/mcp            # the root: five tools, reaches everything
npx -y @aisa-one/mcp seo        # one category, its tools listed directly
npx -y @aisa-one/mcp apollo     # one provider and nothing else
npx -y @aisa-one/mcp --help

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

https://mcp.aisa.one/seo/mcp

60

316

DataForSEO, Semrush, Ahrefs

https://mcp.aisa.one/sales/mcp

79

79

Apollo, Similarweb, creator discovery

https://mcp.aisa.one/social/mcp

56

56

X, Instagram, Reddit, Pinterest, YouTube

https://mcp.aisa.one/finance/mcp

48

48

market data, crypto, prediction markets

https://mcp.aisa.one/search/mcp

30

30

Tavily, Exa, Perplexity, Firecrawl, Oxylabs

https://mcp.aisa.one/<provider>/mcp

one provider

—

26 of them

Counts move as the catalogue does. The live ones, and every provider endpoint, are at mcp.aisa.one/servers, generated per request by the running service.

What it costs

search, get_details and list_categories are free. use and batch_use are billed per call at the same prices as the AIsa REST API, with no seat and no monthly minimum for the MCP itself. Every call takes max_price_usd, and one that would cost more is refused before any charge.

A 402 says which of two things is missing — balance, or the Hive GTM Growth subscription — and where to get it. Prices are at aisa.one/pricing.

Reading more

License

MIT

Available Tools

5 tools
batch_useRun up to 20 operationsA
Destructive

Execute up to 20 operations concurrently (tool-router's batch_use). Each item answers independently; one failure never cancels the others. Billed per call to your AIsa key.

Inputs: calls (required), search_id, max_price_usd. Returns: object

get_detailsShow operation detailsA
Read-only

Full contract of one or more operations: arguments_schema, response_schema, read_only, side_effects, availability, price, suggested_max_price_usd and known_pitfalls. Free — a quote authenticates like a call but stops before any spend.

price.model distinguishes the sources: quoted is what this account would be charged now, list is the published price, dynamic means the price varies with the request and only a quote states it, composed means the operation runs several upstream calls. suggested_max_price_usd is that estimate with headroom, in the shape use and batch_use take as max_price_usd.

Inputs: arguments, with_quote, operation_id, operation_ids. Returns: object

list_categoriesBrowse the AIsa catalogueA
Read-only

The AIsa catalogue at a glance: categories, the servers in each, tool counts, and the dedicated endpoint to connect if you only need one category. Free; no key needed. (AIsa-only: tool-router has no equivalent.)

Use mcp.aisa.one/mcp?modules=<category> (or mcp.aisa.one/<category>/mcp) to have that category's tools listed directly instead of via search.

Inputs: no named parameters. Returns: object

useRun an AIsa operationA
Destructive

Execute one AIsa operation. Billed per call to your AIsa key.

Answers in tool-router's BatchCallResult shape: successful, data or error {type, status, message, retryable}. Pinned tools in tools/list can also be called directly; this is the way to call anything found through search.

Inputs: operation_id (required), arguments, search_id, max_price_usd. Returns: object

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.2/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: list_categories covers category-level discovery, search finds operations by task, get_details exposes contracts, and use/batch_use execute single or batched operations. There is no meaningful overlap between any pair.

    Naming Consistency4/5

    Names are all lowercase imperative commands with underscores, and the pair use/batch_use is logical. The main inconsistency is that search and use are bare verbs while list_categories and get_details include a noun object, but the pattern remains predictable and readable.

    Tool Count5/5

    Five tools is well-scoped for a gateway server that fronts a huge catalogue: two discovery tools, one detail tool, and two execution tools. Every tool earns its place and the count is appropriate.

    Completeness5/5

    The server covers the full lifecycle of working with the AIsa catalogue: browse categories, search operations, inspect contracts, execute one operation, and execute many operations. No obvious dead ends or missing capabilities for the stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data

    Related MCP Connectors

    • Discover, plan and run tools across your connected business systems through one OAuth MCP endpoint

    • The OpenRouter for tools. One MCP connection gives any AI agent 254 hosted tools, pay per call.

      https://api.toolrouter.com/mcp
    • Real-time data APIs for 50+ commerce, grocery, social and maps platforms over one OAuth MCP server

      https://data.upscrape.com/mcp
    • Your agent needs live data — a competitor's traffic, who to contact there, what people are saying, what Google and ChatGPT answer about you, a company's filings. Normally that is six vendor accounts, six sets of keys and six SDKs. This is one URL. **What you can ask for** • "How much traffic does stripe.com get, where does it come from, and who competes for the same keywords?" • "Find 20 Series-B fintech companies in Germany and the heads of marketing there, with emails." • "Does ChatGPT mention our brand when someone asks for the best CRM — and what does it cite?" • "What is X saying about $NVDA today, and what did the stock actually do?" • "Search the web for this, then scrape the three best pages into markdown." **How to use it** Point any MCP client at https://mcp.aisa.one/mcp and sign in with OAuth — there is no key to create or paste. Then just ask: the agent calls search to find the right operation and use to run it. **Why this rather than the source** 26 sources behind one account and one bill — DataForSEO, Semrush, Ahrefs, Similarweb, Apollo, X/Twitter, Instagram, Reddit, Pinterest, YouTube, Tavily, Exa, Perplexity, Firecrawl, CoinGecko, Kalshi, Polymarket, AgentMail and more, 580+ operations. tools/list returns five tools, not 580, so the introduction does not eat your context window. **What it costs** Finding and inspecting an operation is free. Running one is billed per call at API prices, with no seat and no monthly minimum, and every call takes max_price_usd so an agent cannot overspend by accident. **Where else it reaches** One slice at a time: https://mcp.aisa.one/seo/mcp · /finance/mcp · /social/mcp · /search/mcp · /sales/mcp · /mail/mcp · /gtm/mcp, or a single provider like /twitter-api/mcp. Same account, fewer tools listed, and search still reaches everything. Full list at https://mcp.aisa.one/servers

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Unified MCP server for managing Meta Ads, LinkedIn Ads, Google Ads, GA4, and Search Console with 89 read/write tools, multi-account support, OAuth setup, and safe dry-run mutations.
      MIT
    • A
      license
      C
      quality
      B
      maintenance
      Hosted MCP server for 3926 structured public web-data tools across 488 platform groups, returning clean JSON for search, maps, commerce, social, and finance.
      14
      500
      252 npm
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      One MCP server providing access to 160+ live web data APIs (search, social media, e-commerce, real estate, jobs, travel, news, finance, and more) using dynamic discovery via 4 generic tools to avoid the agent's tool limit.
      5
      4
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides a single MCP endpoint for 90+ tools across 42 backend servers (search, legal, domain, etc.) with per-call credit billing and a single API key.
      1
      MIT