home / mcp / digital asset links api mcp server
MCP Server generated by mcp.ag2.ai
Configuration
View docs{
"mcpServers": {
"ag2-mcp-servers-digital-asset-links-api": {
"command": "python",
"args": [
"mcp_server/main.py",
"stdio"
],
"env": {
"CONFIG": "{\"example_key\":\"example_value\"}",
"SECURITY": "{\"apiKey\":\"YOUR_API_KEY\"}",
"CONFIG_PATH": "/path/to/mcp_config.json"
}
}
}
}You run an MCP server that exposes the Digital Asset Links API to clients using the Model Context Protocol. It lets MCP clients interact with the API through a local or remote transport, enabling you to plug the API into tooling that speaks MCP and manage configuration in a repeatable way.
Start the MCP server in stdio mode to launch it as a local process that you can interact with directly from your tooling. You can connect an MCP client to the server by starting it locally and then pointing the client at the server’s endpoints exposed via the MCP channel. Use this approach when you want a self-contained server instance for development or integration tests.
Prerequisites: Python 3.9+ and the package manager tools you prefer (pip and uv). Ensure you have a suitable runtime environment for running Python applications.
# Prerequisites check
python --version
pip --version
uv --version 2>/dev/null || echo "uv not installed"Install dependencies in editable mode to develop against the MCP server package. You have two common options depending on your setup.
pip install -e ".[dev]"If you prefer using uv to run editable installs, use the following command.
uv pip install --editable ".[dev]"Start the MCP server in stdio mode to run it as a local process. This keeps everything self-contained and easy to test.
python mcp_server/main.py stdioConfigure the server using environment variables to control file paths, configuration payloads, and security keys.
CONFIG_PATH=/path/to/mcp_config.json
CONFIG='{"example_key":"example_value"}'
SECURITY='{"apiKey":"YOUR_API_KEY"}'