Context Board

Context Board connections

Every way to get data on Context Board. Sign in to a service, save a key once, connect Google, paste any API, feed or MCP server, or push from your tools.

Last updated October 2026

Everything that reads or feeds your board lives in one window, called Connect. This page covers each way in, in the order the window shows them.

The Connect window

Open it from any of these.

  • Connect at the top right of the board.
  • Connect on a widget that says Not connected 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).
  • The chat, when you ask it to connect something.

The search box at the top finds any app or service. Paste a link into it and it goes straight to the right form. The left side has three places.

  • Your AI: the AI apps that read and build this board, and your computers. See Your agent and your computer.
  • Your data: what keeps your widgets current.
  • Connected: everything that is connected, and how it is doing.

Your data lists ContextBolt’s own products first, then Apps and services from A to Z, then Free and live. 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.

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 it under More options as you add the source, or later with Edit the source, as often as every 2 minutes or as rarely as once a day. 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.

Services you sign in to

These connect through the service’s own MCP server, with the service’s own sign-in.

ServiceWhat it reads
StripeRevenue, customers, subscriptions
PostHogProduct analytics and insights
LinearIssues, projects and cycles
NotionPages and databases
SentryErrors and issues in production
SupabaseYour database and projects
VercelDeployments and projects
IntercomConversations and customers
Jira and ConfluenceAtlassian issues and pages
SquarePayments and orders
PayPalPayments and invoices
WebflowSites and collections
GranolaMeeting notes
Hugging FaceModels, datasets and Spaces
  1. In Your data, pick the service.
  2. Choose Sign in to and the service’s name. Its own sign-in page opens.
  3. Sign in and approve. Back on the board, it says the service is connected.
  4. Choose what to show from the list of things it can read, or use the Ask button to have your agent or the chat build it.

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.

ServiceThe keyWhat it reads
StripeA restricted key, with Read on Balance and SubscriptionsMRR and your available balance
Lemon SqueezyAn API key, and your storeRevenue for the last 30 days, MRR, payments and orders
PlausibleA Stats API key, and your siteVisitors, visitors today, top pages and sources
beehiivAn API key, and your publicationSubscribers
ButtondownAn API keySubscribers
YouTubeA Google API key with the YouTube Data API turned onA channel’s subscribers
GitHubA token of your ownOpen issues on private repositories
  1. In Your data, pick the service. The form links to the page where the service makes its key.
  2. Paste the key and choose Connect and the service’s name.
  3. Choose what to show.

Two of these live on another page. Stripe’s key form sits under Stripe’s sign-in, and GitHub’s token form is on the GitHub repo page in Free and live.

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.

Google Analytics and Search Console

Both sign in with Google, read only.

  1. In Your data, pick Google Analytics or Google Search Console.
  2. Choose Connect Google Analytics or Connect Google Search Console, and sign in with the Google account that can see your site.
  3. Choose a site under Site.
  4. Tick what belongs on your board, and choose the Add button, which counts the widgets you picked.

Google Analytics reads users, sessions, views, the trend, top pages, channels, countries and a world map. Its widgets show complete days, ending yesterday, and Google can take 24 to 48 hours to finish a day’s data.

Search Console reads clicks, impressions, click rate, position, daily clicks, top queries and top pages. Its widgets show final data ending three days ago, over periods from 7 to 480 days. Google leaves some queries out for privacy, so query totals can differ from site totals.

Each widget starts with the last 28 days. Change the period on the widget itself. Context Board can’t change your Analytics settings or your Search Console sites.

ContextBolt SEO and ContextBolt Bookmarks

ContextBolt SEO and ContextBolt Bookmarks sit first in Your data. 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. The board only runs the free reads, so it never spends a credit. 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.

Free and live

These need no account and no key. Most take one field.

SourceWhat it shows
WeatherCurrent conditions and five days ahead, for a place
News headlinesTop stories from one of 16 feeds, such as BBC, The Guardian, NPR, TechCrunch, The Verge and Ars Technica
Sun and moonSunrise, sunset, daylight and the moon, for a place
Public holidaysThe next public and bank holidays, for a country
GitHub repoStars on any public repository, with open issues and forks
npm downloadsWeekly downloads for any package
Hacker NewsThe front page, Best, Newest, Show HN or Ask HN, with points and comments
Crypto pricesLive prices and the 24-hour move, from CoinGecko
Exchange ratesCurrency rates from the European Central Bank

Any API, feed, calendar or MCP server

Choose Add an API or feed, or paste a link into the search box. The board works out what it is.

  • A JSON API: the likely numbers are one tap each, counts and totals first. The whole answer is one click away. If the API wants a key, add it under Its key or token, and set Sent as to the header it expects. Most take a Bearer token, and some name a header of their own, like X-API-Key. The key is sealed on the board’s server and sent only to that address’s site.
  • An RSS or Atom feed, or a site’s home page that links its feed.
  • A calendar: a link ending in .ics, or a webcal:// link. For Google Calendar, open 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 the next section.

Bring your MCP servers

Choose Add an MCP server to connect the servers you already use in another AI app.

  1. Paste a server’s address, or the whole MCP settings file from the app that has them.
  2. The board lists each server it found and checks its web address.
  3. Servers that need no sign-in connect in one click. The rest offer Sign in. A server that lets no app register itself asks for a key instead.

Not sure where the settings are? Open Where to find them in the window.

AppIts MCP settings
Claude DesktopSettings, 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 is read on the page. The board checks each server’s web address, and keys, tokens and anything else in the file never leave the page. Servers that run as programs on your computer are named and explained, since a web page can’t start them.

With your computer linked, the window also lists the MCP servers it found in your AI apps, ready to choose.

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.

  1. Open the widget’s menu, choose Data and source, then Send it data from your agent or a script.
  2. Choose Make a push key and copy it. A push key can send data and nothing else, and it’s shown only once.
  3. Send a POST to https://board.contextbolt.com/v1/push/<stream>, with the header Authorization: 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.

SendFor
{"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 agent and your computer.

Type it in

For a number you know, open the widget’s menu, choose Data and source, and type it. It stays until you change it, or until something sends a newer one.

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 Analytics and Search Console sit at the top.

Each row says how it’s doing.

  • Connected or Live: working.
  • Needs sign-in: sign in to the service again.
  • Key not accepted: the service stopped accepting the saved key. Save a new one.
  • Not reading: the last read failed. The row says why.

Remove anything you no longer use from its row. Removing a source leaves its widgets with the last data they had.

Ready to try Context Board?
Set it up once, then work from your agent.
See Context Board →