Jurnie

ai.jurniePublished by jurnie.aiv1.0.0Updated Nov 14, 2026

Read your Jurnie meetings, summaries, transcripts and meeting memory from any AI assistant.

VerifiedStreamable HTTPWeb executableKnowledge & MemoryCommunication & Collaboration

Overview

AI-generated overview

Connects an AI assistant to Jurnie so it can read your meetings, summaries, transcripts and meeting memory.

What you can do
  • Read meetings recorded in Jurnie
  • Retrieve meeting summaries and transcripts
  • Recall stored meeting memory for context in conversations
When to use it
Useful when you want an assistant to answer questions about past meetings, pull up summaries or transcripts, or bring earlier meeting context into a conversation without copying it by hand.
Requirements
A remote MCP endpoint at app.jurnie.io reached over streamable HTTP, with OAuth sign-in to a Jurnie account required. No environment variables or headers are declared.
Before you install
Access is granted through OAuth to your Jurnie account, so the assistant can read your meeting content, including transcripts and summaries, which may contain confidential discussion. Review the scopes granted during sign-in and revoke access if no longer needed.

Installation

In SourceWeft

  1. Open Jurnie in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.jurnie%2Fjurnie/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "jurnie": {
      "type": "http",
      "url": "https://app.jurnie.io/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestNov 14, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.