Trace for agents · Pro
Your agent should know what tech is doing today.
Create a key, paste one prompt, done. Your agent gets structured current tech news, notable builds, and practitioner conversations without searching the open web from scratch every time.
Read onlyPro checked on every requestMCP + HTTPS
Step 1
Create your read-only Agent Key
Checking your sign-in…
Step 2
Let your agent do the setup
Zero-config option
Don't configure anything. Paste this to your agent.
Copy the prompt, drop it into Claude, Codex, or Cursor along with your agent key from step 1, and it wires up Trace itself.
Set up the Trace MCP server for me. 1. Ask me for my Trace agent key (a Bearer token I already created). 2. Add an MCP server named "trace" with URL https://www.yourtrace.online/api/mcp, using my key as the Bearer token. Use my client's native MCP config format. 3. Verify it works by fetching today's top 3 tech stories from Trace and summarizing each in one line. Notes: the server is read-only. Machine-readable setup docs: https://www.yourtrace.online/agents/llms.txt
Prefer manual setup? Code and configs
Codex
export TRACE_AGENT_KEY="your_key_here" codex mcp add trace \ --url https://www.yourtrace.online/api/mcp \ --bearer-token-env-var TRACE_AGENT_KEY
Claude, Cursor, and MCP clients
{
"mcpServers": {
"trace": {
"url": "https://www.yourtrace.online/api/mcp",
"headers": {
"Authorization": "Bearer ${TRACE_AGENT_KEY}"
}
}
}
}Custom agents and bots
curl "https://www.yourtrace.online/api/agents/brief?limit=8" \ -H "Authorization: Bearer $TRACE_AGENT_KEY"
Delivery channels
Telegram, WhatsApp, Discord, Slack
Trace supplies the intelligence. Your bot or agent decides where to send it. Any system that can call MCP or HTTPS can fetch the brief and post it into the channel you already use.
What the connection can access
Allowed
- Today’s structured Trace feed
- Grouped news, builds, and conversations
- Summaries, takeaways, timestamps, and source links
Never allowed
- Changing your Trace account
- Publishing, purchasing, or writing data
- Access after the key is revoked or Pro ends
Full machine-readable setup notes: /agents/llms.txt