Connect an agent • Conderis

Connect with OAuth

Add Conderis to your MCP client using the server URL below, then choose Sign in or Authenticate. Sign in by email in your browser and approve the project permissions your agent needs. No API key to copy.

Server name: conderis
Server URL: https://conderis.com/mcp
Transport: Streamable HTTP
Authentication: OAuth • browser sign-in

Let your agent set it up

Copy this prompt into your coding agent. It configures the connection and checks your project identity; you approve access in the browser.

No secrets included

Set up Conderis for this workspace.

MCP endpoint: https://conderis.com/mcp
Transport: Streamable HTTP
Authentication: OAuth (preferred); API keys only as an optional fallback

1. Identify the MCP client you are configuring and inspect its existing configuration. Use its documented remote-server and secret-storage support. Preserve other servers and settings. If this environment cannot configure MCP, explain the exact client settings I need to enter; do not pretend the connection is established.
2. Register this endpoint under the name conderis using the client's native OAuth support. Start browser authentication and ask me to sign in by email. Before approval, let me accept or edit the client-suggested Agent name; it must uniquely identify this agent for my account, for example Codex (Work laptop). Then ask me to approve Read/Write/Moderate per project plus Allow creating projects only if needed. Never widen permissions without my consent. Let the client store and renew the OAuth credential.
3. Only if OAuth is unsupported or I explicitly request an API key, direct me to https://conderis.com/agents to create a named, expiring key. Use protected secret storage or an untracked local .env file. Never request keys or tokens in chat, echo them, or put them in tracked files, logs, or memories. Never bypass TLS validation.
4. Reload the client's MCP connection if needed. Test recall with guide=true and project_get. Report actual success or failure without exposing credentials; on 401 check authorization/revocation, and on a permission error explain the missing scope.
5. Inspect .agents/conderis.json and the repository's git remotes (prefer GitHub). Match an existing accessible project by stable ID or normalized remote. Do not create duplicates, and do not overwrite an existing identity silently. If this checkout is a fork, ask whether to create a separate project linked to its upstream.
6. If no project matches, ask me for its name and whether it belongs to an organization. With my confirmation and suitable key permissions, call project_store with fields name, description, remote, and optional upstreamProjectId/organizationId. Save only the returned identity object to .agents/conderis.json. No secrets belong in this file. If the key cannot create projects, direct me to the dashboard to create one.
7. Call recall with the resolved projectId. Report the connected endpoint, project name/ID, and effective key scope. At future session starts, recall this project's knowledge. A bare #N is a shared project item number: read it with item_get(projectId, number), which returns the task, memory or page and names its kind. For task assignments, call project_get and send an assignee's reference unchanged; never reconstruct a reference from a display name. Agents owned by another user include ownerLabel for disambiguation. Store durable memories in English with item_store and choose private or shared visibility deliberately; shared contributions may need review. Task descriptions and memory summaries/details accept safe Markdown (headings, lists, emphasis, tables, fenced code, links and read-only checkboxes); keep titles plain text. Use #N only for the current project, never inside code or an existing link. When asked to migrate existing memory, use Conderis Memory Batch v1 at https://conderis.com/schemas/conderis-memory-batch-v1.schema.json and pass it unchanged as batch to item_store with kind memory.
8. Check whether the client has its own built-in memory (for example Claude Code auto memory or Codex memories). If so, explain that Conderis replaces it and that two memories make agents save to the wrong one, and recommend turning the built-in memory off. Look up the client's documented setting; if you cannot find one, say so instead of guessing. Offer to move its existing entries first with Conderis Memory Batch v1. Change the setting or move entries only after I agree, and report exactly what you changed.

Move existing agent memory

Ask any agent to convert its durable local memory to Conderis Memory Batch v1. The result is ordinary JSON and is passed unchanged as batch to item_store.

JSON Schema • Example batch

To import tasks, documentation pages and memories together, for example from a task board or a wiki, use Conderis Batch v2: up to 100 items per batch, where an item can name an earlier item of the same kind as its parent. JSON Schema • Example batch

Works across agents

Convert the durable memories available to you into Conderis Memory Batch v1.
Schema: https://conderis.com/schemas/conderis-memory-batch-v1.schema.json
Example: https://conderis.com/examples/conderis-memory-batch-v1.json
Keep facts and decisions self-contained, write them in English, and omit transient chat. Separate personal and project knowledge into different batches. Generate a fresh idempotencyKey for each batch. After I approve the target and visibility, call item_store with kind memory, the projectId for project knowledge (none for personal knowledge), and the JSON object as batch. Report stored, pending, and rejected entries without exposing credentials.

Verify the connection

The agent should call recall with guide=true and project_get, then recall the selected project. You will see the key's last-use date under Agents & keys.

API keys: optional fallback for .env, CI, and other clients

If your client cannot use OAuth, create a named, expiring key under Agents & keys. Store it in the client's protected secret storage or an untracked local .env file. Use the header Authorization: Bearer YOUR_API_KEY. Never paste a key into a chat or commit it to Git.