Terra Config

You can use this MCP server to configure the TerraAPI dashboard with a Model Context Protocol client. It exposes a set of endpoints and tooling that lets you manage destinations, providers, and integrations through an MPC interface, enabling automated, scalable control from your LLM or automation scripts.

How to use

You interact with the Terra MCP server through an MCP client that speaks the MCP protocol. Use the client to fetch available integrations, manage destinations, and configure provider keys. The server supports both remote HTTP endpoints and local stdio-based runtimes. Start by choosing how you want to run the server and then invoke it from your MCP client to perform operations like listing integrations, adding destinations, or updating provider states. You can chain several actions into a single workflow, for example provisioning a destination, validating it, and then activating it for use.

How to install

Prerequisites: you need either the uv runtime (recommended) or Python for running the TerramCP server. You also need your Terra API credentials (TERRA_API_KEY and TERRA_DEV_ID) to configure access to TerraAPI.

Option 1: Install and run with uvx (recommended) and run terramcp through uvx.

# Install the uv runtime
curl -LsSf https://astral.sh/uv/install.sh | sh

# Run the TerramCP server via uvx
# This uses the MCP runtime to launch terramcp
uvx terramcp

# Ensure required environment variables are set when starting
export TERRA_API_KEY=your_api_key_here
export TERRA_DEV_ID=your_dev_id_here

# Start terramcp via uvx with the configured environment
uvx terramcp

Option 2: Install and run with Python (pip) and start terramcp as a module.

pip install terramcp

# Run TerramCP using the Python module
export TERRA_API_KEY=your_api_key_here
export TERRA_DEV_ID=your_dev_id_here

python -m terramcp

Configuration notes and security

When configuring TerramCP for your environment, supply your Terra credentials as environment variables in the runtime you choose. These credentials are required for authenticating with TerraAPI.

Keep credentials secure: avoid embedding keys in code or configuration files that travel with your source control. Use your deployment environment’s secret management to inject TERRA_API_KEY and TERRA_DEV_ID at startup.

Troubleshooting and tips

If you encounter connection issues, verify that the required environment variables are available to the runtime and that the TerraAPI endpoint is reachable from your network. Use a minimal configuration first to ensure the server starts, then add destinations or providers incrementally to isolate issues.

Available tools

terra_get_integrations

Retrieve the list of available integrations that the MCP server can expose to clients.

terra_get_detailed_integrations

Obtain a detailed list of supported integrations, filtered by developer-enabled integrations and the requirement for SDK usage.

get_destinations

Fetch the configured destinations that the server can interact with.

get_developer_destination_credentials

Retrieve credentials for a specified developer destination.

delete_destination

Remove a destination from the configured list.

set_destination_state

Activate or deactivate a destination.

add_developer_destination

Add a new developer destination with details like type, host, port, and credentials.

ping_developer_destination

Check if a developer destination is reachable.

set_provider_keys

Store provider keys for a given provider resource.

get_provider_keys

Retrieve stored provider keys for a provider resource.

get_developer_providers

List providers available to developers.

add_providers

Add new providers to the available set.

deactivate_provider

Disable a provider.

set_provider_state

Activate or deactivate a provider.

get_providers_by_popularity

Rank providers by popularity.

add_custom_credentials

Add custom credentials for a specific provider.

get_custom_credentials

Retrieve custom credentials for a provider.