
decentralised-art/mcp
Developer toolsЭта страница переведена автоматически. Технические детали смотрите в оригинале. Открыть оригинал
This repository provides the decentralised.art MCP server and its decentralised-art-mcp CLI. It exposes format-agnostic protocol operations under the core.* namespace.
Обзор
This repository provides the decentralised.art MCP server and its decentralised-art-mcp CLI. It exposes format-agnostic protocol operations under the core.* namespace. Agents can read the full decentralised.art documentation in markdown, starting from https://decentralised.art/llms.txt. The MCP bundles the complete, unabridged llms-full.txt as well as individual platform pages: agents can read them through MCP resources or core.documentation, without visiting the website. Start with getting-started for account onboarding, then read llms-full for system-wide concepts and good practices before designing operations. If you are a user of this repo, the important question is simple: - install it - run it as an MCP server - register it in your MCP-capable host - use it When the MCP server is running, an MCP host can use tools such as: - core.documentation - core.create_account - core.connector_exists - core.get_connector - core.get_transformation - core.get_condition - core.
README
Показан фрагмент оригинального README. Открыть оригинал.
mcp
This repository provides the decentralised.art MCP server and its decentralised-art-mcp CLI.
It exposes format-agnostic protocol operations under the core.* namespace.
Agents can read the full decentralised.art documentation in markdown, starting from
https://decentralised.art/llms.txt.
The MCP bundles the complete, unabridged llms-full.txt as well as individual
platform pages: agents can read them through MCP resources or core.documentation,
without visiting the website. Start with getting-started for account onboarding,
then read llms-full for system-wide concepts and good practices before designing operations.
If you are a user of this repo, the important question is simple:
- install it
- run it as an MCP server
- register it in your MCP-capable host
- use it
What users get
When the MCP server is running, an MCP host can use tools such as:
core.documentationcore.create_accountcore.connector_existscore.get_connectorcore.get_transformationcore.get_conditioncore.transformation_existscore.condition_existscore.get_feed_pagecore.get_feed_stream_replaycore.list_formatscore.get_formatcore.get_accountcore.get_noncecore.create_connectorcore.create_transformationcore.create_conditioncore.simulate_connectorcore.prepare_publicationcore.publish_entitycore.confirm_publicationcore.execute_connectorcore.ensure_preflightcore.build_parent_connector
It also exposes these MCP resources (URI prefix decentralised-art://resource/):
core.getting-startedcore.primercore.docs.llms-full— completellms-full.txt, preserved verbatimcore.docs.tutorialcore.docs.mcpcore.docs.sdkcore.docs.api-referencecore.docs.aboutcore.docs.roadmap
Hosts that expose only tools can read the identical text through
core.documentation. It defaults to getting-started; pass topic to select
a guide. Long guides return next_start_line for continuation.
To read the full platform documentation through a tool, call
core.documentation with {"topic":"llms-full"} and follow next_start_line
until it is null. Resource-capable hosts can read the complete text at
decentralised-art://resource/core.docs.llms-full in one request. Bundling makes
the text discoverable; the host still has to load it into the agent’s context.
Fresh accounts without user-supplied keys
A new signing identity does not require the user to supply an existing private
key. On macOS/Linux, an agent can call core.create_account with a stable ID:
{"account_id":"draft_owner"}
The server generates and persists the Ethereum key locally, returning only
account_id, address and created. Retrying the same ID reuses that identity.
Pass account_id to draft creation, preflight and publication tools. No gas,
funds or API request is needed to create an account; drafts also spend no gas.
Установка
npx @modelcontextprotocol/inspector \Конфигурация
{
"mcpServers": {
"decentralised-art": {
"type": "stdio",
"command": "/path/to/mcp/.venv/bin/python",
"args": ["-m", "decentralised_art_mcp.server", "stdio"],
"env": {
"PYTHONPATH": "/path/to/mcp/src",
"API_BASE": "https://api.decentralised.art/chain",
"PRIVATE_KEY": "<optional>",
"DECENTRALISED_ART_TIMEOUT": "15",
"DECENTRALISED_ART_ARTIFACT_ROOT": "/path/to/mcp/decentralised-art-mcp-artifacts"
}
}
}
}