Jenda

is.jendaPublished by jenda.isOfficial publisherv1.1.0Updated Nov 7, 2026

Your trips: who's going, the plan, and the costs. File receipts and see who owes whom.

VerifiedStreamable HTTPWeb executableLocation & LifestyleFinance

Overview

AI-generated overview

A remote Jenda server that lets an assistant work with your trips — attendees, the plan and costs — and file receipts to track who owes whom.

What you can do
  • Manage trip details: who is going and what the plan is.
  • Track trip costs and file receipts.
  • See balances showing who owes whom.
  • No individual tools are listed in the manifest, so exact actions are not documented.
When to use it
When you use Jenda to organize shared trips and want an assistant to help with attendees, plans, costs or receipt-based expense splitting without switching apps.
Requirements
A remote endpoint at jenda.is reached over streamable HTTP; OAuth sign-in is required. No packages, environment variables or headers are declared.
Before you install
Sign-in is via OAuth, so the assistant gets access to your Jenda trip and expense data. It may read or change trip plans, costs and receipts, which can affect who is recorded as owing money; confirm changes before they are applied.

Installation

In SourceWeft

  1. Open Jenda 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/is.jenda%2Fjenda/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": {
    "jenda": {
      "type": "http",
      "url": "https://jenda.is/api/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

2
  1. v1.1.0LatestNov 7, 2026
  2. v1.0.0Nov 4, 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.