Connect your data to Context Board
Every way to get data on Context Board. Sign in to an app, save a key once, bring your MCP servers, paste any API, feed or calendar, or push from your tools.
Everything that keeps your widgets current lives in one window, called Connect. This page covers each way in.
Pick your route
| What you have | Where to go |
|---|---|
| An app like Stripe, Lemon Squeezy, Linear or Search Console | Apps and services |
| MCP servers you already use in Claude, Cursor or another app | Bring your MCP servers |
| Any API, RSS feed or calendar link | Any API, feed, calendar or MCP server |
| Weather, news, prices or stars, with no account | Free and live |
| A script, cron job, n8n, Zapier or Make | Send it from your tools |
| A number you know | Type it in |
Your AI agent can also put data on the board. That’s on Your AI and your computers.
The Connect window
Open it from any of these.
- The Connect plug icon at the top right of the board.
- Connect on a widget that has no data yet. The window opens on the places that widget’s data most likely comes from.
- Connect data in the command bar (Ctrl K or ⌘ K, or /).
- A step on the Connect your tools checklist, at the bottom left.
The left side has three places.
- Your AI: the AI apps that read and build your board, and your computers.
- Your data: everything that keeps your widgets current.
- Connected: everything that’s connected, and how it’s doing.
The search box at the top reads Search apps and services, or paste a link. Paste a link and it goes straight to the right form. Paste an MCP settings file and it opens Add an MCP server.
Your data lists Apps and services from A to Z, then Free and live, then Your own, the servers you connected by their address. Each app’s tile says how it connects: Sign in, API key or Coming soon. Two buttons at the top, Add an MCP server and Add an API or feed, add anything else.
Every form tries what you entered and shows what the widget will say before anything is added. Then choose Add to the board. If you started from a widget, the button reads Connect to and the widget’s name.
Apps and services
Services you sign in to
These connect through the service’s own MCP server, with the service’s own sign-in.
| Service | What it reads |
|---|---|
| Stripe | Revenue, customers, subscriptions |
| PostHog | Product analytics and insights |
| Linear | Issues, projects and cycles |
| Notion | Pages and databases |
| Sentry | Errors and issues in production |
| Supabase | Your database and projects |
| Vercel | Deployments and projects |
| Intercom | Conversations and customers |
| Jira and Confluence | Atlassian issues and pages |
| Square | Payments and orders |
| PayPal | Payments and invoices |
| Webflow | Sites and collections |
| Granola | Meeting notes |
| Hugging Face | Models, datasets and Spaces |
- In Your data, pick the service.
- Choose Sign in to and the service’s name. Its own sign-in page opens.
- Sign in and approve. Back on the board, it says the service is connected.
- Choose what to show from the list of things it can read, or choose Ask and your agent’s name to build it.
Hugging Face needs no account for what it shares, so its button reads Connect Hugging Face.
The board only runs a remote server’s tools that read. Nothing in your account changes. If a sign-in expires, the source says Needs sign-in, and Sign in to the service again fixes it.
Services that take a key
Some services are read with a key you save once. Every board can then show that service’s data, with nothing more to paste.
| Service | The key | What it reads |
|---|---|---|
| Stripe | A restricted key, with Read on Balance and Subscriptions | Available balance, MRR, revenue and payments |
| Lemon Squeezy | An API key, and your store | Revenue for the last 30 days, MRR, payments and orders |
| Plausible | A Stats API key, and your site | Visitors, visitors today, top pages and sources |
| beehiiv | An API key, and your publication | Subscribers |
| Buttondown | An API key | Subscribers |
| YouTube | A Google API key with the YouTube Data API turned on | A channel’s subscribers |
| GitHub | A token of your own | Open issues on private repositories |
- In Your data, pick the service. The form links to where the service makes its key, or to its API docs.
- Paste the key and choose Connect and the service’s name.
- Choose what to show.
Two of these sit on another page. On Stripe’s page, the key form is under Or show your available balance with a Stripe key. GitHub’s is on the GitHub repo page in Free and live, under Private? Use your own GitHub token.
The key is sealed on the board’s server and never shown again. The board only reads with it, and only from that service’s own address. To swap it, open the service and choose Change key.
ContextBolt SEO and ContextBolt Bookmarks
Both sit in the Apps and services list. Each signs in with your email, the eight-character code we send, and Allow.
- ContextBolt SEO: your Search Console performance, quick wins, recent and tracked research, saved research, credits left and page index status. Its widgets only run the free reads, so they never spend a credit. In the chat, your agent can also run fresh keyword, ranking, backlink and AI visibility lookups, which spend credits as they do in any other app. Needs a ContextBolt SEO plan.
- ContextBolt Bookmarks: your recent bookmarks, a search of everything, and your topics. The board only reads, so nothing in your library changes. Needs ContextBolt Bookmarks Pro.
Google Search Console
Signs in with Google, read only.
- In Your data, pick Google Search Console.
- Choose Connect Google Search Console, and sign in with the Google account that can see your site.
- Choose a site under Site.
- Tick what belongs on your board: search performance, clicks, impressions, click-through rate, average position, top queries and top pages. Then choose the Add button, which counts the widgets you picked.
Its widgets show final data, in Pacific time, ending three days ago. Each starts with the last 28 days, and you can change the period on the widget itself, from 7 to 480 days. Google leaves some queries out for privacy, so query totals can differ from site totals.
Google Analytics
Coming soon. Google is reviewing our access to Analytics, so its tile says Coming soon and connecting opens once Google approves. Boards that already connected it keep working.
Google Calendar
Coming soon on Calendar boards. Google is checking the calendar permission first, so its tile says Coming soon until Google approves. Until then, a calendar widget shows any Google calendar through its secret iCal link: see Any API, feed, calendar or MCP server.
Bring your MCP servers
Already use MCP servers in Claude, Cursor or another app? Put what they know on your board, with no setup twice.
- In Your data, choose Add an MCP server.
- If your computer is linked, the servers it found in your Claude Code, Codex and Claude app are listed first. Pick the ones you want.
- Otherwise, paste a server’s address, or the whole MCP settings file from the app that has them. Not sure where it is? Open Where to find them.
- The board checks each server and gives it one button. Connect needs nothing more. Sign in opens the server’s own sign-in. Add a key is for a server that lets no app register itself. Check it is for an address that may have a key in it.
- Choose what to show.
When several need no sign-in, one button at the top connects them all.
| App | Its MCP settings |
|---|---|
| Claude Desktop | Settings, Developer, Edit Config |
| Claude Code | ~/.claude.json, or .mcp.json in a project |
| Cursor | ~/.cursor/mcp.json |
| VS Code | .vscode/mcp.json |
| Windsurf | ~/.codeium/windsurf/mcp_config.json |
| Codex | ~/.codex/config.toml |
| Gemini CLI | ~/.gemini/settings.json |
What you paste stays on the page. The board checks each server’s web address. Keys, tokens and anything else in the file never leave the page.
What comes from a linked computer is only each server’s name and web address, never a key, and the board adds only the ones you choose. A server whose address holds a key stays on your computer, and the page asks you to paste its settings instead.
Servers that run as programs on your computer can’t run on the board, since it’s on the web. The page names them. Your AI app keeps using them, and can put what it finds on the board. Or turn on Use my existing MCPs, and the board’s chat uses them on your computer.
Any API, feed, calendar or MCP server
- In Your data, choose Add an API or feed, or paste a link into the search box.
- Paste the address and choose Check it. The board works out what it is: A JSON API, A feed, A calendar or An MCP server.
- If it wants a key, add it under Its key or token and set Sent as to the header it expects. Most APIs take a Bearer token. Some name a header of their own, like X-API-Key.
- Choose what the widget shows, then Add to the board.
What each one gives you:
- A JSON API: under What should the widget show?, the likely numbers are one tap each, counts and totals first. Something else from what it sent opens the whole answer. It refreshes every 15 minutes unless you change it.
- An RSS or Atom feed, or a site’s home page that links its feed.
- A calendar: an iCal link, including webcal:// links. For Google Calendar, open its Settings, pick your calendar, open Integrate calendar and copy the Secret address in iCal format. You can also paste it straight into a calendar widget, under Show your events.
- An MCP server: see Bring your MCP servers.
If an API refuses without a key, the form says This API wants a key. Add it above. Then choose Try with this key. The key is sealed on the board’s server and sent only to that address’s site.
Free and live
These need no account and no key. Most take one field.
| Source | What it shows |
|---|---|
| Weather | Current conditions and five days ahead, for a place |
| News headlines | Top stories from one of 16 feeds, such as BBC, The Guardian, NPR, TechCrunch, The Verge and Ars Technica |
| Sun and moon | Sunrise, sunset, daylight and the moon, for a place |
| Public holidays | The next public and bank holidays, for a country |
| GitHub repo | Stars on any public repository, with open issues and forks |
| npm downloads | Weekly downloads for any package |
| Hacker News | The front page, Best, Newest, Show HN or Ask HN, with points and comments |
| Crypto prices | Live prices and the 24-hour move, from CoinGecko |
| Exchange rates | Currency rates from the European Central Bank |
Send it from your tools
Anything that can make a web request can keep a widget current, like n8n, Zapier, Make, a cron job or a GitHub Action.
- Open the widget’s menu, choose Data and source, then Send it data from your agent or a script.
- Choose Make a push key and copy it. A push key can send data and nothing else, and it’s shown only once.
- Send a
POSTtohttps://board.contextbolt.com/v1/push/<stream>, with the headerAuthorization: Bearer <your push key>and a JSON body.
curl -X POST https://board.contextbolt.com/v1/push/signups \
-H "Authorization: Bearer YOUR_PUSH_KEY" \
-H "Content-Type: application/json" \
-d '{"value": 42}'The panel fills in the stream’s name for you. The body’s shape decides what you send.
| Send | For |
|---|---|
{"value": 42} | A number |
{"points": [{"t": ..., "v": ...}]} | A history |
{"items": [{"label": ..., "value": ...}]} | A list |
{"rows": [...]} | A table |
{"text": "..."} | A report |
In Zapier use Webhooks, in n8n use HTTP Request, and in Make use HTTP, each with the key as a Bearer token. A push the board can’t read is refused, never stored as zero.
Your agent can push data too, with no key to copy. See Your AI and your computers.
Type it in
For a number you know. On a widget with no data yet, choose Type it or Or type it in. On a widget that has a source, open its menu, choose Data and source, then Connect a source, then Type it in. It stays until you change it, or until something sends a newer one.
Put your data on a widget
Once something is connected, the gallery (press A) shows it under Your sources, right below Everything. Each source gets the widgets that can show it, drawn with its real data, plus your own custom widgets for it, marked Yours. One click adds one.
Choose a widget from your data in Connected opens the same place.
When sources update
Sources the board reads run on our server, only while the board is open somewhere. Close it and they pick up again the next time it opens. Nothing refreshes in the background, and nothing sends alerts.
Each source has its own schedule. Set Refresh while the board is open under More options as you add it: every 5 or 15 minutes, every hour, every 6 hours or once a day. Edit the source later goes as often as every 2 minutes. Refresh now in a widget’s menu reads it at once.
If a read fails, the widget keeps the last good value and says, beside it, what went wrong and when. The board never shows a number it didn’t receive.
Connected
Connected lists everything that reads or feeds the board, grouped as AI apps, Computers, Apps the board reads from, Services with your key, Live data and Send-only keys. Google sits at the top.
Each row says how it’s doing.
- Connected or Live: working.
- Needs sign-in: sign in to the service again, or choose Add a key if it asks for one.
- Key not accepted: the service stopped accepting the saved key. Save a new one.
- Not reading: the last read failed. The row says why.
- Reconnect: sign in with Google again.
- Not used yet: an AI app’s access that hasn’t read the board yet.
- Waiting: a send-only key that hasn’t sent anything yet.
- On or Off: whether a linked computer is on.
Remove anything you no longer use from its row. Removing a source leaves its widgets with the last data they had.
Limits
Each account holds up to 100 sources, 20 MCP server connections and 200 streams, and takes up to 20,000 pushes a day.