Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion Makefile
Original file line number Diff line number Diff line change
Expand Up @@ -66,7 +66,7 @@ docs_serve: ## Build docs and start frontend server
docs_watch: ## Build docs and watch for changes
python scripts/docs.py build --source docs --destination ${FRONTEND_PATH}/content/docs --watch

docs_publish: ## Tag and push `docs-next` ref
docs_publish: ## Tag and push `docs` ref
git tag -d docs && git tag docs && git push --force origin docs

docs_publish_dev: ## Tag and push `docs-next` ref
Expand Down
6 changes: 3 additions & 3 deletions docs/5.advanced/8.mcp.md
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@ With DipDup's MCP integration, you can:

There are three types of MCP primitives (citing from the docs):

- **Resources** are **application-controlled** and allow to expose data and content that can be read by clients and used as context for LLM interactions.
- **Resources** are **application-controlled** and allow servers to expose data and content that can be read by clients and used as context for LLM interactions.
- **Tools** are **model-controlled** and enable servers to expose executable functionality to clients, such as interacting with external systems, performing computations, and taking actions in the real world.
- **Prompts** are **user-controlled** and enable servers to define reusable prompt templates and workflows that clients can easily surface to users and LLMs

Expand Down Expand Up @@ -183,11 +183,11 @@ async def tool():
result = await mcp.call_tool('my_tool', {})
```

For a low-level access you can use `dipdup.mcp.server` singleton to interact with the running server.
For low-level access, you can use `dipdup.mcp.server` singleton to interact with the running server.

### Interacting with running indexer

DipDup provides [management API](../7.references/4.api.md) to interact with the running indexer. For example you can use it to add indexes in runtime.
DipDup provides [management API](../7.references/4.api.md) to interact with the running indexer. For example, you can use it to add indexes at runtime.

You can use `ctx.call_api` to get nice plaintext output or `ctx.api` to access the datasource directly.

Expand Down