Guide

A-Share Data in Muse

Muse is Meta’s personal AI Agent. It has no native MCP settings page, but a custom connector can point at our remote MCP server, so you can query A-share data from mobile or Mac.

Muse uses a custom connector, not an MCP dropdown

Today and Grok Bot expose a clear custom-MCP entry. Muse uses Settings → Connectors → ask Muse to create a custom connector.

Muse runs on a cloud VM and can only reach public HTTPS endpoints, which fits our remote MCP server. No local process is needed.

  • URL: https://api.ashareapi.com/mcp
  • Auth: Authorization: Bearer <ashareapi Key>
  • Transport: Streamable HTTP
  • ⛔ localhost and local MCP are not supported

Before you start

  • Muse app (mobile, Mac or WhatsApp entry)
  • An ashareapi API key; use a separate read-only key
  • Verify the key: GET /v1/quote?code=sh600519

Connect: ask Muse to create a custom connector

Open Settings → Connectors and create a custom connector, or ask Muse in chat. Send this with your key:

Message to Muse
Connect this hosted MCP server as a custom connector.
Name: ashareapi
URL: https://api.ashareapi.com/mcp
Transport: Streamable HTTP
Authentication: HTTP header "Authorization" with value "Bearer <YOUR_ASHAREAPI_KEY>"

Muse may show the connector it generated or ask you to approve it. Confirm the URL is api.ashareapi.com and the auth header is Bearer.

Verify: list tools, then ask three questions

Ask Muse to list the MCP tools. Confirm ashare_quote, ashare_finance and ashare_kline appear.

Ask inside Muse
Get the latest quote for sh600519

Get 600519 revenue for 2026Q3

Show the last 30 daily K-lines for 600519

401 or no tools

401
Auth treated as another type
Ask for Remote MCP + Authorization: Bearer
No tools
URL public HTTPS
Use https://api.ashareapi.com/mcp
Connection fails
Trailing slash
Try https://api.ashareapi.com/mcp/
Header ignored
Custom connector limits
Review the generated connector and approval card
Timeout
Result too large
Lower count / limit / num, then batch

Which tier: upgrade by workload

Quotes and K-lines can start on the base allowance; financials, batch calls, screening and research need a higher tier. See the full pricing page.

Trial
¥9.9 one-time
10k calls · 30 req/min · 24 endpoints
Financials, dividends, sectors; light research
Standard
¥29.9 one-time
100k calls · 120 req/min · 46 endpoints
Daily research, notices, fund flow and more
Pro
¥99 one-time
500k calls · 300 req/min · 80 endpoints
Screening, batch financials, agent research
Institutional
¥199/month
100k/day · 600 req/min · 96 endpoints
Teams, multiple IPs, institutional research

¥9.9 Trial · ¥29.9 Standard · ¥99 Pro · Institutional · Full pricing

Boundaries

  • ✅ Read-only data lookup and research summaries
  • ⛔ No automated trading, brokerage connection or return promises
  • ⛔ Not investment advice; explain numbers by API date and definition
  • ⛔ No stale close presented as a live quote; no missing fields filled with zero

FAQ

Does Muse natively support MCP?

Muse does not expose a native MCP settings page like Today, but it supports custom connectors that can point at a public hosted MCP server.

Do I need a local server?

No. Muse reaches our remote MCP server from the cloud. Only local servers need a tunnel.

How do I configure Bearer auth?

When asking Muse to create the custom connector, specify Authorization: Bearer <Key> and verify it on the approval card.

Why are no tools showing?

Check the URL and public reachability first, then the auth header. Muse may require you to approve the generated connector.

Last updated: 2026-10-31

Muse custom-connector entry follows Meta Help “How Muse works with Connectors”; hosted-MCP behavior follows public third-party testing; MCP URL and Bearer auth follow the live ashareapi endpoint.

Related

← All tutorials