What connects
Integrations
Contextely has two connectors and no per-vendor code. A source is either a read-only SQL query against a Postgres-compatible database, or an MCP server you give a URL and two tool names. Everything below is one of those two with the parts we can know already filled in.
The two connectors
Adding a system of record is configuration, not an integration somebody has to build for your logo. That is the whole trade this product makes, and the cost of it is the honest list further down.
A read-only SQL query
Postgres, Supabase or Neon. A connection string and two queries: one that lists what should become memory, one that re-reads a single row by its id. Contextely refuses anything that is not a single SELECT or WITH and opens the session read-only, so a source cannot write to your database even when the query is wrong.
Any MCP server
A Streamable HTTP endpoint, the name of a tool that lists records, and the name of a tool that fetches one. Contextely connects as an MCP client, both to ingest the first time and to re-read a record when its memory object passes its TTL.
Connected and checked
A system appears here once somebody has run the whole path against it: connect, sync, retrieve, let a memory object pass its TTL, and watch it re-fetch. Not once the code exists, and not once the endpoint is documented.
Postgres
checked end to endOne table or view becomes memory, re-read row by row when a memory object passes its TTL.
You need: A read-only connection string, and the names of the columns that hold each row's identifier, title and text.
Built, not yet checked
These are configured and selectable inside the product, and each one was written against the service's published tool list. None of them has been run end to end by us against a real account, so none is being claimed as supported. If you connect one and it works, or it does not, tell us and this page changes.
GitHub
tokenEvery issue in one repository becomes memory, and stays current as issues are edited.
GitHub documentationLinear
tokenOne Linear team's issues become memory, re-read when they go stale.
Linear also offers a browser sign-in flow. Contextely uses the API key path, which is the one that keeps working unattended when a memory object goes stale at three in the morning.
Linear documentationSentry
tokenOne project's issues become memory, so an agent can answer what is currently breaking.
Sentry documentationLedgeur
tokenMeeting notes and transcripts become memory, so an agent can answer from what was actually said.
A meeting does not change after it happens, so a long TTL costs nothing here. The notes attached to one can, which is why the TTL is not infinite.
Ledgeur documentationNotion
browser sign-inThe pages matching one saved search become memory, re-read from Notion when they go stale.
Notion's server has no way to list everything, only to search, so a source covers one saved search rather than a whole workspace. Connect several if you want several areas.
Notion documentationSlack
browser sign-inOne channel's messages become memory, treated as a record of decisions rather than a conversation.
Slack's server requires workspace admin approval before anything can connect, and it does not support automatic client registration, so a self-hosted Contextely needs its own Slack app.
Slack documentationGoogle Drive
browser sign-inThe documents matching one saved search become memory, with the full text one call away.
Google's Drive MCP server is a developer preview, so it can change without notice. It also does not support automatic client registration, so a self-hosted Contextely needs its own Google OAuth application.
Google Drive documentation
Bring your own
Neither list is a limit. Anything that publishes an MCP server is reachable right now, and any Postgres-compatible database is reachable through the SQL connector, without waiting for a tile to appear above.
Any MCP server
Anything that speaks MCP over Streamable HTTP becomes memory, with no code written on either side.
You need: The endpoint, the name of a tool that lists records and the name of a tool that fetches one, plus the argument names each expects.
Any SQL query
Whatever a read-only SELECT returns becomes memory, joins and filters included.
You need: A read-only connection string and two queries: one that lists, one that re-reads a single row.
Why there is no logo grid
An enterprise search platform sells connector count, and a connector estate is a real cost: each one has an auth flow, a rate limit, a schema, and a permission model somebody has to map onto yours and then maintain forever. Contextely takes the other side of that trade. Two connectors you configure yourself in a few minutes, and no waiting list for a logo.
The cost of the trade is exactly what this page shows. If a system does not publish an MCP server and does not sit in a database you can query, Contextely does not reach it, and no amount of copy here changes that.
What Contextely does not reach
- A product with no MCP server and no queryable database. There is no scraping path and no browser automation.
- A record with no stable identifier. The re-fetch key is what makes freshness work, so a source without one cannot be kept honest.
- A file share. Contextely condenses records, not documents, and there is no file parsing step in the product.
- A source's own permission model. Entitlement is expressed in Contextely, per source and per member. It does not mirror the ACLs of the system it read from.
8 systems are selectable in the app today. Connect one in the quickstart, or read how a source's credential is stored.