Set up an OAuth connection
Open Settings → Integrations and copy the MCP server URL into an OAuth-capable remote MCP client. FactNot publishes OAuth discovery metadata, uses authorization code flow with PKCE, and asks you to approve the requested permissions in the browser.
- Use the configured URL shown in Settings instead of copying an access token or creating an API key.
- Dynamic registrations are public clients: no client secret, PKCE required, and bounded redirect metadata.
- Only named client recipes that have passed end-to-end verification are shown in the app.
Choose capabilities deliberately
The legacy fuu.mcp permission covers fact search and private fact creation. Additional scopes opt a client into workspace records, private sources, public changes, or separately reviewed management actions.
- Workspace access covers actor-authorized facts, people, entities, libraries, views, spaces, and verification requests, including reversible archive and restore.
- Source access covers URL and text capture, bounded source-body reads, ingestion retries, draft creation, and the companion file-upload flow.
- Passwords, authentication changes, billing, account deletion, ownership transfers, permanent bulk deletion, private messaging, and staff actions stay browser-only.
Source text remains private
Saving or uploading a source does not make its body public. Captured text is owner-only by default, full bodies are returned only in bounded chunks to clients with source permission, and uploaded files are never embedded as base64 in MCP messages.
- A public fact may cite a private source; publishing the fact never publishes its source body or uploaded file.
- The assistant cannot invent or submit a source permission basis; you choose source rights directly in FactNot.
- File uploads use a short-lived one-time upload URL and a 20 MB limit before private extraction.
Publication requires confirmation
Public fact and view changes use prepare, review, and execute steps. The approval is short-lived, single-use, and bound to your account, OAuth client, action, target, payload, and exact record version.
- A compatible assistant may show an ordinary confirmation form; otherwise FactNot returns a browser review URL.
- Execution rechecks ownership, permissions, current version, service switches, entitlement, and approval expiry.
- Publishing source bodies or assets always finishes in the browser so you can make the rights decision yourself.
Troubleshoot a connection
MCP authorization is evaluated on every request, so account, consent, legal, service-switch, and access-mode changes apply to access tokens that were already issued.
- 401 means the bearer token is missing or invalid. Reconnect from the client rather than pasting tokens into support messages.
- 403 can mean a missing scope, revoked consent, required policy acceptance, an unavailable account, or premium access required in the current mode.
- 503 means the MCP service is disabled or its policy check could not be completed. Retry later; repeated reconnects will not bypass it.
- Native clients may omit Origin. Browser clients must use a trusted configured Origin.
Disconnect and revoke
Open Settings → Integrations, find the connected client, and choose Disconnect. FactNot revokes that client's consent and refresh grants for your account, and its existing access tokens fail the next consent check.
- Disconnect clients you no longer recognize or use.
- Also remove FactNot from the assistant if you want to clear its local connection metadata.
- A later reconnect starts a new browser consent flow and does not restore the old grant automatically.