Oassis MCP server for web access

Let an MCP-compatible client discover the web tools it can call. Configure the public server URL in your client, then test discovery before running a workflow.

Connect the server

https://api.oassis.dev/mcp

Choose a client that supports remote HTTP MCP servers. The exact configuration and availability depend on the client; consult its remote-server settings. Connecting Oassis does not mean a client automatically uses it for every web request.

Discover the tools

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/list"
}

Send this JSON-RPC request by POST after the client's MCP initialization handshake. The tool catalogue is the authoritative source for each tool's current arguments.

• web_scrape, web_scrape_batch, web_batch_status
• web_map, web_crawl, web_crawl_status
• web_session_open, web_act, web_session_close
• web_search_exa and the web_task_* research tools, with their separate requirements

Call a scraping tool

{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "tools/call",
  "params": {
    "name": "web_scrape",
    "arguments": {
      "url": "https://example.com",
      "formats": [
        "markdown"
      ]
    }
  }
}

Free MCP access

MCP includes 100 trial credits for scrape and map. All other paid tools require an API key and sufficient credits. Use the owning API key for task status and cancellation; x402 tasks use their access_token. HTTP operations use x402 payments without an account.

Continue with MCP integration, x402 payments or the OpenAPI reference.