jitprompt

com.jitpromptPublished by jitprompt.comOfficial publisherv1.0.0Updated Oct 24, 2026

Just-in-time instructions for agents: upload docs, serve only the sections each turn needs.

VerifiedStreamable HTTPWeb executableKnowledge & MemoryAI & ML

Overview

AI-generated overview

Remote MCP server that serves just-in-time instructions to agents: upload docs and only the sections each turn needs are delivered.

What you can do
  • Upload documentation and instruction material to a hosted service.
  • Serve only the sections relevant to the current turn instead of whole documents.
  • Provide agents with just-in-time instructions drawn from the uploaded material.
  • Connect over a remote streamable HTTP endpoint authenticated with a bearer API key.
When to use it
Useful when an assistant needs large or frequently changing instruction sets and you want to avoid loading entire documents into context each turn. Suited to teams that maintain shared documentation and want agents to pull only the relevant parts.
Requirements
A remote endpoint at app.jitprompt.com over streamable HTTP. A bearer API key created in the jitprompt app, sent in the Authorization header. A jitprompt account and network access.
Before you install
The Authorization header carries a secret API key; keep it private and revocable. Uploaded documents are stored on a third-party hosted service, so avoid sending confidential material you do not want held there. The tool list is not published, so verify what it can read or change before connecting.

Installation

In SourceWeft

  1. Open jitprompt in the dashboard and add it to a workspace.
  2. Connect Authorization token 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/com.jitprompt%2Fjitprompt/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.

{
  "mcpServers": {
    "jitprompt": {
      "type": "http",
      "url": "https://app.jitprompt.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestOct 13, 2026

Score

67% 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
  • 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.