Watt MCP
Watt data, in your agents.
Give agents direct, governed access to Watt’s data through the Model Context Protocol. Integration takes about 30 minutes.
When to use it
Built for agents that need context.
Ground agents
Answer with real records instead of guesses.
Research on demand
Let agents find and combine signals as they work.
Build audiences
Turn a plain-English brief into a measured set of people.
Extend assistants
Add Watt to Claude and other MCP clients.
What you can access
One delivery layer across Watt's data.
MCP reaches the same data as every other delivery method. Scope depends on what your agreement covers.
Industries
EnergyManufacturingConstructionTransportationFinanceRetail & Commerce
Data types
IntentEmploymentContactsFirmographicsFinancialOperationalProprietary
Need something else? Watt can source it.Discuss your data needs
How it works
A question in. Grounded context out.
ClientYour agent
DeliveryWatt MCP
Refined dataSignal Graph
ResponseTool results
- Standard protocolTo confirmWorks with any client that speaks MCP.
- Described toolsTo confirmAgents see what each tool does and when to use it.
- Rights-aware accessTo confirmResults respect the permitted uses in your agreement.
- Governed by scopeTo confirmAgents only reach what your agreement covers.
Developer preview
What a connection looks like.
A sketch of the shape. Implementation lives in the docs.
Authorized through OAuthIllustrative. Server and tool names not final
Client config
{
"mcpServers": {
"watt": {
"url": "https://mcp.wattdata.ai/mcp"
}
}
}Tool call
find_signals({
"query": "field engineers in the Permian Basin"
})
→ 12 signals
"Oil & gas field engineers" 41K fresh
"Recent job change, energy" 9K freshDocsGetting startedAPIMCPBulk and formatsSecurity and rightsSupportRead the docs
Delivery methods