An agent that cannot launch pgokf-mcp itself calls it over HTTP, and every such request carries a bearer token. A token is shown once, when it is minted; only its digest is kept, so it can be revoked here but never read back. The roles are a ladder: a reader token searches and reads the catalog, a builder token may also build workspace plugins, a writer token may also write documents into a content bundle, and an admin token may also create, refresh, enable, disable, and retire bundles. What a writer token contributes arrives unverified whatever it claims, so a person still reviews it. The two writing roles need the MCP server to hold a writer connection of its own (OKF_PG_WRITER_URL); without one their tools say so. A token is minted for the tenant this site serves, an MCP endpoint accepts only tokens minted for its own, and this page shows that tenant's tokens alone. Revoking takes effect with the next request.
Minting needs the writer connection (OKF_PG_WRITER_URL).
Token {{ m.name }} ({{ m.role }}) - copy it now; it is not shown again.
{{ m.token }}
The client sends it as Authorization: Bearer … to the MCP endpoint (POST /mcp); a plugin built on the Plugins page expects it as OKF_MCP_TOKEN.
No token has been minted, so the HTTP endpoint refuses every request.
{% else %}| Name | Role | Minted by | Minted | Change |
|---|---|---|---|---|
{{ t.name }} |
{{ t.role }} | {{ t.created_by }} | {{ t.created_at|datetime }} |