Tracxn MCP Server Python API Docs | dltHub

Build a Tracxn MCP Server-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.

Last updated:

Tracxn is a market intelligence platform providing a REST API for accessing detailed data on companies, investors, and funding transactions. The REST API base URL is https://platform.tracxn.com/api/2.2 and all requests require an API key for authentication.

dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv add "dlt[hub]" and start loading Tracxn MCP Server data in under 10 minutes.


What data can I load from Tracxn MCP Server?

Here are some of the endpoints you can load from Tracxn MCP Server:

ResourceEndpointMethodData selectorDescription
companies/companiesGETSearch and filter company records
company_details/companies/{id}GETGet detailed profile of a specific company
transactions/transactionsGETSearch funding rounds and transaction history
investors/investorsGETSearch investor profiles and portfolio data
acquisitions/acquisitionsGETSearch acquisition deal records
sectors/sectorsGETList or search industry sectors

How do I authenticate with the Tracxn MCP Server API?

The API uses an API key for authentication, typically passed in the request headers (e.g., 'X-API-KEY').

1. Get your credentials

To obtain your Tracxn API credentials, navigate to the Tracxn platform at https://tracxn.com. Log in to your account and navigate to Products > Data Solutions > API to explore and generate your API token or access key. If the option is not visible, contact your account manager or Tracxn support, as API access is typically provided as a premium data solution.

2. Add them to .dlt/secrets.toml

[sources.tracxn_mcp_server_source] api_key = "your_tracxn_api_key_here" # Or if using the TRACXN_ACCESS_TOKEN environment variable: access_token = "your_tracxn_access_token_here"

dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.


How do I set up and run the pipeline?

Set up a virtual environment and install dlt:

uv init uv add "dlt[hub]"

1. Install the dlt AI harness:

uv run dlthub ai init --agent <your-agent> # <agent>: claude | cursor | codex

This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →

2. Install the rest-api-pipeline toolkit:

uv run dlthub ai toolkit install rest-api-pipeline

This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →

3. Start LLM-assisted coding:

Use /find-source to load data from the Tracxn MCP Server API into DuckDB.

The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.

4. Run the pipeline:

uv run python tracxn_mcp_server_pipeline.py

If everything is configured correctly, you'll see output like this:

Pipeline tracxn_mcp_server_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset tracxn_mcp_server_data The duckdb destination used duckdb:/tracxn_mcp_server.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs

Inspect your pipeline and data:

uv run dlthub show

This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.


Python pipeline example

This example loads search_companies and search_investors from the Tracxn MCP Server API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:

import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def tracxn_mcp_server_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://platform.tracxn.com/api/2.2", "auth": {"type": "bearer", "token": api_key}, }, "resources": [ {"name": "companies", "endpoint": {"path": "companies"}}, {"name": "transactions", "endpoint": {"path": "transactions"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="tracxn_mcp_server_pipeline", destination="duckdb", dataset_name="tracxn_mcp_server_data", ) load_info = pipeline.run(tracxn_mcp_server_source()) print(load_info)

To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.


How do I query the loaded data?

Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.

Python (pandas DataFrame):

import dlt data = dlt.pipeline("tracxn_mcp_server_pipeline").dataset() sessions_df = data.companies.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM tracxn_mcp_server_data.companies LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("tracxn_mcp_server_pipeline").dataset() data.companies.df().head()

See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.


What destinations can I load Tracxn MCP Server data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

DestinationExample value
DuckDB (local, default)"duckdb"
PostgreSQL"postgres"
BigQuery"bigquery"
Snowflake"snowflake"
Redshift"redshift"
Databricks"databricks"
Filesystem (S3, GCS, Azure)"filesystem"

Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.


Next steps

Continue your data engineering journey with the other toolkits of the dltHub AI harness:

  • data-exploration — Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.
  • dlthub-platform — Deploy, schedule, and monitor your pipeline in production.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform

Was this page helpful?

Community Hub

Need more dlt context for Tracxn MCP Server?

Request dlt skills, commands, AGENT.md files, and AI-native context.

Available Pipelines