Skip to content
AstroWay/api v2.95.1 · agent-setup
all systems operational

Cline

Connect the AstroWay API to Cline over MCP. For Cline, stdio is the most reliable transport.

Get an API key in the dashboard. For free testing use a sandbox aw_test_* key — it doesn’t spend credits.

Open Cline → MCP Servers → Configure to edit cline_mcp_settings.json. Paste one of the blocks below and restart Cline.

Stdio (npx) — local subprocess, env-var auth, offline-ready. Recommended for Cline:

cline_mcp_settings.json
{
"mcpServers": {
"astroway": {
"command": "npx",
"args": ["-y", "@astroway/mcp"],
"env": { "ASTROWAY_API_KEY": "aw_live_YOUR_KEY" }
}
}
}

Hosted (HTTP) — if your Cline version supports remote servers:

cline_mcp_settings.json
{
"mcpServers": {
"astroway": {
"url": "https://mcp.astroway.info/mcp",
"headers": { "Authorization": "Bearer aw_live_YOUR_KEY" }
}
}
}

Tell Cline in chat: “List the AstroWay tools” — or ask it to call a free reference tool, such as fetching the list of zodiac signs. If a result comes back, the connection works.

  • 401 / invalid key — make sure the key is prefixed aw_live_* or aw_test_* and isn’t revoked. Check it in the dashboard.
  • Tools don’t appear — fully restart Cline and verify the path to cline_mcp_settings.json.
  • -32602 validation errors (stdio) — update the package: npm i @astroway/mcp@latest. Schemas are regenerated from the live spec.

See all clients — Agent setup.

Was this helpful?
Suggest an edit

Last updated: