MCP Server

Mimir turns published research into answers you can check. The MCP server exposes that to any assistant that speaks the Model Context Protocol, so instead of copying results between a browser and your tools, your assistant queries the literature directly and works with what it finds.

Coverage is strongest in materials science, and questions from adjacent chemistry and physics are answered from the same corpus. Every answer carries citations, and every citation links to the publisher. Mimir does not host papers, so you always read the original at the source.

• ask_scientific_literature

  Ask a question in natural language and get an answer with citations to the papers it draws on.

• list_conversations

  List the conversations created through MCP, so an agent can pick up where it left off.

• get_conversation

  Read a conversation back in full, including its citations and references.

• share_conversation

  Publish a conversation to a public link that anyone can read.

Assistant connections are available on Pro or Partner plans. Upgrade to connect your own tools and agents to Mimir.

Your assistant draws on the same query allowance your plan already includes, so what it asks counts the same as what you ask in the web app.

Running something larger, or need an arrangement beyond a standard plan? Email contact@mimirsystems.ai.

Endpoint

https://mcp.mimirsystems.ai/api/mcp

Transport

Streamable HTTP. Every request is self contained, so there is no session to keep alive and nothing to reconnect.

Authentication

OAuth 2.1, or an API key sent as Authorization: Bearer.

OAuth

The recommended path, and the one to use if your client supports it. Clients like Claude Code and the Claude apps discover the server and sign you in through your browser. There is no credential to copy, create, or rotate, and access follows your account.

API keys

For clients that cannot run an OAuth flow, and for headless machines with no browser to sign in from. Create a key in your account settings, then paste it into your client configuration. A key is shown once, acts on your behalf, and can be revoked at any time from the same place.

Replace the placeholder with your own key. If your client uses OAuth, leave the authorization header out entirely and let it sign you in.

{
  "mcpServers": {
    "mimir": {
      "type": "streamable",
      "url": "https://mcp.mimirsystems.ai/api/mcp",
      "headers": {
        "Authorization": "Bearer emk_1a2b3c4d5e6f_YOUR_KEY_SECRET"
      },
      "anythingllm": {
        "autoStart": true
      }
    }
  }
}