Fodda Knowledge Graphs

Expert-curated knowledge, brand, research & earnings intelligence — 31 tools, 220+ graphs.

Fodda Knowledge Graphs is an MCP server that gives AI agents access to expert-curated intelligence across four domains: general knowledge, brand analysis, research, and earnings data. The server exposes 31 tools and more than 220 graphs through a stdio transport, making it suitable for agents that need structured, pre-built intelligence rather than raw database queries.

The server is configured with two environment variables: FODDA_API_KEY for authentication and FODDA_API_URL to specify the API endpoint. It is published on npm under the package identifier fodda-mcp at version 1.32.1 and its source is available on GitHub.

Because the facts do not include the individual tool names, the specific actions each tool exposes cannot be described in detail here. What is documented is that the 31 tools collectively surface the curated graph data — covering brand intelligence, research findings, and earnings information — to any agent connected over stdio. This makes it a fit for workflows where an agent needs to query structured, domain-specific knowledge without building its own data pipeline.

This server is not a general-purpose relational database connector and is not designed for Postgres or any other SQL engine. It requires a Fodda API key, so access depends on having a valid account with the publisher.

Use cases

  • Query brand intelligence graphs to support competitive analysis workflows
  • Retrieve expert-curated research data within an AI agent pipeline
  • Access earnings intelligence to support financial research tasks
  • Integrate structured knowledge graphs into an agent without building a custom data layer

When to use it

  • When an agent needs pre-curated brand, research, or earnings intelligence without querying raw data sources
  • When the workflow runs over stdio transport and can supply a Fodda API key
  • When 220+ pre-built graphs cover the knowledge domain required by the agent

When not to use it

  • When the use case requires querying a Postgres or other SQL database directly
  • When no Fodda API key is available, as the server requires authentication
  • When a transport other than stdio is needed
  • When the agent requires real-time or self-hosted data rather than a third-party curated API