Skip to content

SignalForge

Every system you run, in one place.

Dashboards and reports across your cloud, business apps, HR, finance and internal APIs.

Connect it once.

Microsoft Entra ID, Azure Resource Manager, Active Directory (on-prem), Jira Cloud, Atlassian Organization, Cursor and more, synced into one model on their own schedule.

See all 13 connectors

Report on it from then on.

Charts, tables and cards joined across systems. Schedule them, or export to PDF, Excel and CSV.

Explore SignalForge

Ask it in plain words.

The Forge Assistant answers from your data, as you: it runs the query with your permissions, draws the chart from the rows it read and shows how it got there. It proposes reports and dashboard changes; a person applies them. Included from Pro.

The assistant and its guardrails

Or from your own AI tools.

SignalForge is an MCP server. Any AI client that connects to a remote MCP server signs in through the browser as one of your users and reads only what that user can read. An administrator chooses the tools, per agent if need be, and nothing can be deleted through it. Part of Enterprise.

How AI clients connect
Address
https://<your SignalForge host>/mcp
Transport
Streamable HTTP
Sign-in
OAuth in your browser, as you
mcp.read
Read what you can read
mcp.write
Save reports and dashboards, only where an admin allows it
Tools
Search, query, aggregate, explain a change, run reports, read dashboards, sync status
Deletes
None, ever
What a client connects to: no key to paste, no program to install.

Reports that arrive on their own.

Put any dashboard on a schedule. It goes out as a PDF to the people you name, with no one logging in.

Any dashboard as a PDF: the same cards, charts and tables, paged for print.
On a schedule, the PDF arrives by e-mail for the people you name.

Your own API? No code.

Describe an internal REST API in a YAML file: where it lives, how to sign in, how it pages, which fields matter. SignalForge syncs its inventory like a built-in connector and builds the first dashboard from it.

How custom connectors work
name: Warehouse Inventory
baseUrl: https://inventory.internal.example
authentication:
  type: BearerToken
dataSourceSchemas:
  - items-schema.yaml
---
name: Items
endpoint: /v1/items?limit=100
primaryKey: id
responseDataPath: data
pagination:
  type: cursor
  nextPagePath: next_cursor
columns:
  - { name: id, type: string }
  - { name: status, type: string }
  - { name: updatedAt, type: datetime, sourcePath: updated_at }
defaultReports:
  - name: Items by Status
    reportType: Chart
    chartType: Donut
A whole connector: one system, one data source, one starter chart.

See your own systems in SignalForge.

Nothing is charged until you choose a paid plan.