Skip to content

Connect your own agent or app

Anything that speaks MCP can read a Notedigit repository. For agents, scripts and internal tools where a browser sign-in is awkward, use a personal access token: it acts as you, reads only the repositories you are assigned to, and every call is logged.

Before you start

  • Notedigit is running on your server and the repository is connected.
  • You are assigned to the repository; the token can read nothing you can’t.
  • Your agent can make HTTPS POST requests, or uses an MCP client library with streamable HTTP transport.

The endpoint looks like this

  1. Step 1: Create a personal access token

    In Notedigit, open Settings → Access tokens and create a token. Copy it right away: it is shown once.

    Tokens last 90 days and can be revoked at any time. Store it like a password, in your agent’s secret store rather than in code.

  2. Step 2: Copy the endpoint and the handshake

    Open the repository in Notedigit. On the MCP endpoint card, the Your own app tab shows a ready-made first request for this repository.

  3. Step 3: Open a session

    Send initialize with your token as a bearer token. The endpoint accepts POST only; GET and DELETE answer 405.

    curl -X POST https://notes.your-company.com/mcp/<repository-id> \
      -H "Authorization: Bearer YOUR_TOKEN" \
      -H "Content-Type: application/json" \
      -H "Accept: application/json, text/event-stream" \
      -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-11-25","capabilities":{},"clientInfo":{"name":"your-app","version":"1.0.0"}}}'
  4. Step 4: Keep the session id

    The response carries an MCP-Session-Id header. Send it back on every later request, together with the same Authorization header, and follow the standard MCP sequence: an initialized notification, then your calls.

  5. Step 5: Call the tools

    List the tools, then call them. There are three, all read-only and Markdown-only: search (query, optional limit up to 50), read_file (path to a .md note) and list_files (optional prefix, up to 500 paths).

    {"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"search","arguments":{"query":"deploy checklist","limit":5}}}
  6. Step 6: Mind the limits and the log

    Each token can make 60 MCP requests a minute. Every session is recorded in Notedigit under MCP connections as authenticated with a token, with the token’s prefix, so automation is easy to tell apart from people.