# jitprompt

> jitprompt is an MCP server for agent instructions. Upload your docs as they are; jitprompt splits them into sections and serves your agent a live table of contents plus only the sections each turn needs, instead of one giant system prompt.

jitprompt is in pre-launch: request an invite at https://www.jitprompt.com/early-access/.

## How it works

- Upload Markdown, plain text, PDF or Word files as they are. jitprompt splits each document into titled, summarized sections (a model is used once, at ingest — never on search).
- Your agent connects over MCP (streamable HTTP, bearer API key bound to one namespace) at https://app.jitprompt.com/mcp.
- Three tools: `get_toc` (a live table of contents of every document), `get_section` (open a section by id), `search_instructions` (search by what the agent is about to do; returns whole sections).

```sh
claude mcp add --transport http jitprompt https://app.jitprompt.com/mcp --header "Authorization: Bearer imcp_…"
```

## Plans

- **Free** — $0: 1 namespace; 3 documents per namespace; 5 ingestions per day, per organization; Documents up to 50,000 characters; Current version only · no search sandbox
- **Starter** — $4.99/month: 3 namespaces; 10 documents per namespace; 10 ingestions per day, per organization; Document version history; Search sandbox
- **Pro** — $49.99/month: 10 namespaces; Unlimited documents; 100 ingestions per day, per organization; Document version history; Search sandbox

## FAQ

### How is this different from RAG over my docs?

Three ways. Search is driven by what the agent is about to do, not by the user's message. Results are whole sections, never fragments. And the agent always sees a map of what exists, so it can go straight to a section instead of hoping a search finds it.

### Do I have to restructure my docs?

No. Upload Markdown, plain text, PDF or Word files as they are. jitprompt splits them into sections, titles and summarizes each one, and you can review every section in the web app exactly as your agent will see it.

### Is there an LLM call on every search?

No. A model is used once, at ingest, to structure and summarize your documents. Retrieval is a search over the index, so it stays fast and predictable.

### Which agents can connect?

Any MCP client that supports streamable HTTP with a bearer key: Claude Code, the Anthropic API's MCP connector, agent frameworks and CI jobs. Connector UIs that require signing in, like Claude.ai, are on the roadmap.

### What happens when I change a document?

Edit it in the browser or replace it through the API, and it's re-ingested. The table of contents is built live on every call, so agents see the new version as soon as it's ready. On paid plans the previous versions are kept, so a bad edit is one restore away.

### How is my data isolated?

Every API key is bound to one namespace and can read nothing else. Keys are stored hashed and rate limited, and another organization's pages simply don't exist for you.

## Pages

- [Home](https://www.jitprompt.com/): overview
- [Product](https://www.jitprompt.com/product/): features, walkthrough, plans and FAQ
- [Early access](https://www.jitprompt.com/early-access/): request an invite
- [Documentation](https://docs.jitprompt.com/): setup, concepts, API reference — and its own index for models: https://docs.jitprompt.com/llms.txt

## Legal

- [Data Processing Addendum](https://www.jitprompt.com/dpa/)
- [Privacy Policy](https://www.jitprompt.com/privacy/)
- [Subprocessors](https://www.jitprompt.com/subprocessors/)
- [Terms of Service](https://www.jitprompt.com/terms/)