morphiaone-mcp
An MCP server that lets Claude, Cursor or any MCP client digitise product shade colours through the MorphiaOne V1 API: retain a photo, measure regions, propose a candidate, review it and stage it as an unpublished catalogue draft. It is a thin client of the public API, so your key's scopes, rate limits, credits and test mode apply as they do anywhere else.
Install
pip install morphiaone # the CLI that writes the client configuration
morphiaone mcp install --client claude-code # or cursor, claude-desktop
morphiaone mcp install adds one morphiaone server to the client's configuration
and leaves the others as they are. It runs morphiaone-mcp if it is on your PATH
(pipx install morphiaone-mcp), otherwise uvx morphiaone-mcp. --print shows the
entry without writing it.
The server reads the key from MORPHIAONE_API_KEY. Claude Code and Cursor expand that
reference when they start the server, so no key is written to their files. Claude
Desktop expands nothing, so its file would hold the key: the command writes it only
with --store-key. Use a test-mode key, or one with only digitisation.read and
digitisation.write, and revoke it when you stop.
MORPHIAONE_BASE_URL defaults to https://api.morphiaone.ai.
What the agent can do
The tools it sees are the ones your key holds every scope for. Give an agent
digitisation.read and digitisation.write and it proposes; a person reviews and
stages in the Platform. Staging is not publishing: a draft renders nothing until
someone publishes it.
Guide, tools and scopes: https://docs.morphiaone.ai/guides/ai-agents
morphiaone-mcp --version prints the installed version; include it when you report a
problem, with the request_id of any refused call.
Metadata
Release files for morphiaone-mcp 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| morphiaone_mcp-0.1.0.tar.gz | 13.4 kB | With provenance | Details for morphiaone_mcp-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| morphiaone_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for morphiaone_mcp-0.1.0-py3-none-any.whl |
Total release size: 26.4 kB
Release files / morphiaone_mcp-0.1.0.tar.gz
| Download URL | morphiaone_mcp-0.1.0.tar.gz |
|---|---|
| Size | 13.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0eb8751a76fdaa92fefbe9f6cefe6dd890e6a0f90e36e86d070316290cce1b98
|
|
BLAKE2b-256 checksum How to use checksums |
04c54e2115d585bd77fe7b1943517b01a0c3cf094453867bf076b237f79cc0fa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 9, 2026.
Transparency logRelease files / morphiaone_mcp-0.1.0-py3-none-any.whl
| Download URL | morphiaone_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 13.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a2a0c723162df192e41d3c1e2f8c332c3eebc83b50baf114465d8ef3b1e9bf9a
|
|
BLAKE2b-256 checksum How to use checksums |
c054443f83a120c245d2d73ab3bb89ec9d2d94d1e6d649dfed85d50ce398c82a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 9, 2026.
Transparency logSecurity for morphiaone-mcp 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for morphiaone_mcp-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 9, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.