Let your Agent use Currents directly
- Invite-only
- Read-only
- Chinese & English
Understand
One integration, two layers
MCP: the tool layer
Five read-only tools exposed over the MCP protocol: hot board, search, report detail, event timeline, and daily digest. Credentials are issued individually after an invite.
Skill: the semantics layer
The Skill teaches the agent when to use which tool and how to preserve event confidence and the Watching-board distinction. MCP provides capability; the Skill keeps it correct — together they are Currents Agent Access.
Ask right after connecting
Five read-only tools
- currents_hot
- The current event board: a high-confidence main board plus a Watching section, narrowable to news, products, or research.
- currents_search
- Full-text search over published reports by topic, organization, model, or phrase.
- currents_item
- Read one report: score context, translations, and source links.
- currents_event
- Read a multi-source event: timeline, confidence, lifecycle, heat history, and merge lineage.
- currents_daily
- Fetch the latest Currents Daily or an exact-date archive.
Configure
Connect over MCP
With your invited credentials, add the MCP endpoint to your client configuration. Replace placeholders such as TOKEN with the issued values.
Codex
# ~/.codex/config.toml
[mcp_servers.currents]
url = "https://currents-mcp.ethanpier.com/mcp"
http_headers = { "Authorization" = "Bearer TOKEN" }Claude Code
claude mcp add --transport http currents \
https://currents-mcp.ethanpier.com/mcp \
--header "Authorization: Bearer TOKEN"Generic MCP client
{
"mcpServers": {
"currents": {
"type": "http",
"url": "https://currents-mcp.ethanpier.com/mcp",
"headers": {
"Authorization": "Bearer TOKEN"
}
}
}
}Install & verify
Install the Skill
Load the Skill in the client that uses the MCP server, so the agent learns Currents query strategy and event semantics.
- Get the Skill package (attached to the invite email, or via the agreed path).
- Place SKILL.md in your client's skill directory (e.g. ~/.codex/skills/currents/ for Codex).
- Start a new session — Skills load at session start; an already-open session won't pick it up.
Verify the integration
After configuring, open a new session and verify in order:
- Ask "What's hot in AI today?" — the agent should call currents_hot and keep main board vs. Watching distinct.
- Ask about a specific topic — the agent should call currents_search, then follow up with currents_item or currents_event by ID.
- Ask for today's daily summary — the agent should call currents_daily.
Success criteria: all five tools are discoverable and callable; answers preserve confidence and Watching semantics; configuration survives a client restart.
Troubleshoot & apply
Troubleshooting
- Tools not visible
- Confirm you edited the file your client actually reads, then fully restarted the client (not just a new window).
- 401 Unauthorized
- The credential is missing, mistyped, or in the wrong place. Check the Authorization: Bearer TOKEN header against the invite email.
- Skill not active
- Skills load at session start — open a new session after installing, and confirm SKILL.md sits in the client's expected skill directory.
- Configuration lost after restart
- It was written to a transient session instead of the persistent config file. Re-add it at the persistent location shown above.
Request an invite
Access is invite-only for now: reach out through the site's public contact channel, mention your client and use case — no other personal information needed.
Running into access issues?