ElasticGraph MCP Server
This provides a Model Context Protocol (MCP) server for ElasticGraph using the MCP python-sdk.
Setup
- Install dependencies:
# make install
uv sync
source .venv/bin/activate
- Run the server:
The server runs on port 3000, and though there are no logs displayed, it is actively waiting for input.
# make server
uv pip install .
elasticgraph-mcp-server
Development
MCP Inspector
You can test your MCP server with Anthropic's Inspector. To start:
- Run the following command, which starts the server as a subprocess and launches the Inspector UI:
# make inspector
mcp dev src/elasticgraph_mcp/server.py
- Open your browser and navigate to http://localhost:5173 to access the MCP Inspector UI.
Goose
Add a development build to Goose:
- In Goose, navigate to Settings > Extensions > Add.
- Set Type to StandardIO.
- Obtain the absolute path to the project’s CLI:
# Get the path and copy it to your clipboard
realpath .venv/bin/elasticgraph-mcp-server | pbcopy
- Type
uv runthen paste that path
uv run </path/to/elasticgraph_mcp/.venv/bin/elasticgraph-mcp-server>
- Enable the extension and verify that Goose recognizes your tools.
Ask goose: What tools and resources for ElasticGraph do you have?
Development commands
This project uses make for common development tasks. To see all available commands, run:
make help
Using Goose to help with development
You can use Goose to improve this MCP server. To teach goose about MCP, follow these steps:
Setting Up a Goose Session
- Navigate to this MCP Server Directory:
cd ai_tools/elasticgraph-mcp-server
- Prepare a Temporary Directory:
mkdir tmp
touch tmp/.gitignore
echo "/*" > tmp/.gitignore
- Create MCP Instructions File:
Copy MCP instructions from MCP LLM instructions to a new file:
touch tmp/mcp_for_llm_instructions.md
- Start a Goose Session:
goose session
Try this prompt:
First, learn about MCP servers from
tmp/mcp_for_llm_instructions.md. Then, see the current MCP server I'm building insrc/elasticgraph_mcp/server.py. Now
Metadata
Release files for elasticgraph-mcp-server 0.1.1
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 | |
|---|---|---|---|---|
| elasticgraph_mcp_server-0.1.1.tar.gz | 14.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| elasticgraph_mcp_server-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 22.3 kB
Release files / elasticgraph_mcp_server-0.1.1.tar.gz
| Download URL | elasticgraph_mcp_server-0.1.1.tar.gz |
|---|---|
| Size | 14.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
196834b68c8c886722c81e5fa5268a62ce0b69eb38e40ac787a577fbbcb7876b
|
|
BLAKE2b-256 checksum How to use checksums |
39eccc01c64f3fc117013ddbccd065fec5635ec39816261f23af27bc9baa3d89
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Release files / elasticgraph_mcp_server-0.1.1-py3-none-any.whl
| Download URL | elasticgraph_mcp_server-0.1.1-py3-none-any.whl |
|---|---|
| Size | 8.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
eaf13e3bf3cc73bed08bff305d15d182f855ba612e5614d681d8382688055626
|
|
BLAKE2b-256 checksum How to use checksums |
10e4e0df9a4215ba2d039744954abdb42a52670913a1957d15b67fd166b6c644
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Security for elasticgraph-mcp-server 0.1.1
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.