Console
Connect agents to the same current state.
Choose your client, approve access, then read records or propose an update. Every integration uses the database’s ontology, policies, history, and provenance.
Connect your assistant
- Open your database from Databases, then select Connections.
- Choose MCP and your client. Copy the database endpoint exactly as shown.
- Follow the client’s setup. When account approval is supported, sign in to ConceptMem and authorize the application through OAuth.
- Select the database and an access level your role allows: Read and write to propose updates, or read-only to inspect state.
- Enable the connection in your conversation and ask the agent to list the database’s classes and fields.
Listing classes inspects vocabulary. To read current facts, ask the agent to find and inspect an existing record. For an empty database, follow the write, read, and history tutorial.
Choose authentication
| Path | Requirements |
|---|---|
| OAuth | Your own account and access to the database. No API key is needed. Viewers can authorize read-only MCP access. |
| API key | A database API key for REST or a client that requires one. Owners and editors can create keys in Settings. Save the secret when shown; it cannot be retrieved later. |
Keys carry agent authority. Invite teammates through Members instead of sharing credentials. Manage your application grants and keys in the database’s Settings.
First-use checklist
- Define what can exist: inspect or define vocabulary for one useful record.
- Authorize a connection: approve OAuth access or create an API key if needed.
- Propose your first update: inspect the receipt, read current state, and check history.
The console checklist records configured access, not a live connection test. Confirm the tools are enabled by making a read request from your client.
Read every write receipt
Processing can complete with applied changes, skips, blocking refusals, or pending review. Save the returned canonicalId or entity UUID for later reads and updates; a raw source reference can differ from the stored identity.
Applications and protocol reference
For REST, choose the REST API tab and use its hosted request example with a database API key. REST availability is independent of npm publication.
Agent connections use remote MCP over Streamable HTTP. The MCP reference covers tool arguments, profiles, and recovery. Use the endpoint shown for your database rather than constructing one from its name.