# AIsa-public/AIsa-mcp-server [Health: Active]

**Category:** 🔗 Aggregators  
**Repository:** https://github.com/AIsa-public/AIsa-mcp-server  
**GitHub Stars:** 0  
**npm Downloads (last month):** 201  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/aisa-public-aisa-mcp-server

## Description
Search, inspect and run data APIs for SEO and AI visibility, finance, social, web search, sales and agent mail through a few meta-tools, with spending caps.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "aisa-mcp-server": {
    "command": "npx",
    "args": ["-y","@aisa-one/mcp"],
    "env": {
      "AISA_API_KEY": ""
    }
  }
}
```

**Requires environment variables:** `AISA_API_KEY` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What AIsa-public/AIsa-mcp-server MCP server does

AIsa-public/AIsa-mcp-server MCP server provides one MCP entry point for AIsa’s catalogue of more than 580 operations across 26 servers. The available areas include SEO and AI visibility, finance, social platforms, web search, sales, and agent mail. Instead of exposing the entire catalogue as individually listed tools, the root endpoint presents five meta-tools that let an agent discover and invoke the operation it needs.

The five tools are `search`, `list_categories`, `get_details`, `use`, and `batch_use`. Discovery operations are free. Execution is billed per call using the prices of the corresponding AIsa REST API operations. Both execution tools accept `max_price_usd`; a request above that limit is rejected before charging.

## How it works

The primary endpoint is `https://mcp.aisa.one/mcp`, using Streamable HTTP. An agent can search in plain language, review candidate operation IDs and input schemas, inspect a selected operation’s response shape and other details, and then invoke it. `batch_use` can run up to 20 operations under the same price cap.

AIsa-public/AIsa-mcp-server MCP server also supports narrower endpoint paths for categories and providers. SEO, sales, social, finance, search, and GTM paths change which tools are listed, while the root catalogue remains reachable through the meta-tools. Provider-specific paths are available as well. The live inventory and counts can change as the catalogue changes.

Authorization normally uses OAuth. A client that makes an unauthenticated request receives a 401 response containing the protected-resource discovery information; the client can register, open a browser, and obtain consent. A bearer token from the AIsa console can be supplied instead, which is useful for SSH or CI environments.

For clients that cannot speak remote MCP, the `@aisa-one/mcp` npm package provides a local stdio bridge. It forwards requests to the remote service, supports the OAuth browser flow, caches the token, and accepts `AISA_API_KEY` from the environment. The bridge can use the root, a category, or a provider as its target.

## Setup and configuration

Remote-capable clients can be configured with the Streamable HTTP URL. Claude Code and Codex have command-line examples in the project documentation; Cursor, VS Code, Windsurf, and other clients can use a URL-based MCP entry.

A stdio configuration can launch `npx -y @aisa-one/mcp`. Passing a category such as `seo`, or a provider name such as `apollo`, narrows the listed tools while retaining the meta-tool model. Additional arguments are passed through to the underlying remote bridge.

AIsa-public/AIsa-mcp-server MCP server does not require an account before OAuth discovery, but paid operations require the relevant AIsa balance or, where indicated by the service, the Hive GTM Growth subscription. The repository identifies the project as MIT licensed.

_Full upstream README: https://allmcps.com/mcp/aisa-public-aisa-mcp-server/readme_