The MCP server

One URL. It speaks both the current streamable-HTTP transport and the older HTTP+SSE one, so it works with clients that have not caught up to the latest spec.

https://api.knowmee.io/mcp

Authentication is OAuth 2.1 with PKCE. Your client runs the flow itself — you will see a KnowMee sign-in, approve the connection, and land back in the assistant.

Claude

Settings → Connectors → Add custom connector, and paste the URL above. Claude shows a Connect card the first time a tool is called; approve it once.

ChatGPT

Settings → Connectors → Add, then paste the URL above.

Cursor, Windsurf, Zed

Add it as a remote MCP server in the editor’s settings, or drop the snippet below into the MCP config file.

{
  "mcpServers": {
    "knowmee": {
      "url": "https://api.knowmee.io/mcp"
    }
  }
}

Four tools, and reading is separated from writing so you can see at a glance which one changes anything.

get_context

Reads. Returns your record — projects, roles, skills, education, what you are doing now — with dates, any metric the source actually stated, and the source behind each fact.

search_record

Reads. Searches the full text of your original sources, not just fact titles, so “have I used Rust?” finds the README that proves it.

get_application_data

Reads. Your details in the shape a form wants: name, headline, links, top projects, skills. Public facts only unless you ask for more.

log_career_event

Writes. Adds something you just did to your record. Always returns a visible confirmation — capture you cannot see is capture you cannot correct.

Nothing here can delete a fact, change a fact, publish your page, or reach any service you have connected. The write tool appends to a log and nothing else.

The record is built to refuse invention, and that carries through to what an assistant says using it.

• A fact only exists if a source says it. No number appears that was not stated in a README, a résumé or your own words.
• Every fact carries the source it came from, so an assistant can attribute rather than assert.
• Facts you have not confirmed carry a confidence below 1.0, and the server tells the model to hedge on those rather than state them flatly.
• When the record has nothing on a subject, the server says so explicitly and instructs the model not to fill the gap with something plausible.

A connected client reads your record and only yours, through a token issued to that client alone. There is no shared index across users and no way for one connection to reach another account.

Revoke a connection at any time from your KnowMee settings or from the client itself; access ends immediately. The full detail is in the privacy policy.

Transport

Streamable HTTP, with legacy HTTP+SSE also served. POST for calls, GET for the stream, DELETE to end a session.

Auth

OAuth 2.1, PKCE S256, RFC 8707 resource indicators. An unauthenticated call returns 401 with WWW-Authenticate.

Discovery

RFC 9728 protected-resource metadata at /.well-known/oauth-protected-resource/mcp.

Scopes

knowmee:record.read and knowmee:record.write. There is no wildcard scope.

Audience

Tokens issued for a different resource are refused. We never forward a token we were handed.

Check discovery without connecting:

curl -s https://api.knowmee.io/.well-known/oauth-protected-resource/mcp

Write to support@knowmee.io with the client you are using and what you saw. See also support.