Integrations and connectors: your agent holds them, not Hoshin

hoshin.app has no connector to your ERP, your CRM, your MES or your project tool, and it holds no access to them. That is a choice. In a company where people work with AI agents, the agent is what holds the connectors, the MCP servers and the rights. Hoshin is one source among the others in the agent’s set of sources: the one that carries the strategy.

So this page lists no logos. It says how a figure travels from your systems to your X-Matrix without a connector on our side, what Hoshin itself exposes, and what this choice costs.

Our reading of the word "connector"

A connector, in the usual sense, is a link the vendor builds and runs: the tool logs into your ERP with an account you entrust to it, on its own schedule, and copies what was planned. Each connector is an access you grant to one more vendor, and a list you depend on.

With agents, the link moves. Your agent already reaches your systems, each through that system’s own MCP server or API, with the rights of the person it works for. When it needs the strategy, it reads the X-Matrix the same way. Hoshin does not sit in the middle of your systems; it sits beside them, in the agent’s reach.

What that changes for you

Four consequences, the first three in your favour:

  • No credential of your business tools is stored at hoshin.app. We cannot leak an ERP password we never had.
  • Rights stay where they are. An agent reads in your CRM what its user may read there, and writes in the matrix what that user may write there (an API token acts as the admin who created it). Nobody maintains a second map of permissions.
  • No list to wait for. A tool your agent can reach is a tool that works with Hoshin, as soon as it has an MCP server or an API.
  • The link exists only when an agent or a script runs. Nothing syncs by itself in the background.

How a figure travels from your systems to the matrix

This is how it is designed to work; we describe it, we have not yet run it against a real ERP or quality tool. Take the monthly reading of a quality indicator. The agent reads the source in your quality tool, through that tool’s MCP server. It writes the value on the indicator in the matrix, for the period, with where it comes from: which tool, which record, extracted when. At the next review, anyone can see the figure and its origin.

The same goes for a project. An initiative carries a link to its project in your execution tool. The agent follows it, reads progress there, and writes a progress note on the initiative. Tasks and tickets stay in the execution tool: the matrix holds the strategy and its reviews, nothing else.

What Hoshin itself exposes

These are our interfaces. All but the last answer a request or send a signal, and none of those logs into your systems.

  • An MCP server, at hoshin.app/mcp: 44 tools to read and write the matrix, the reviews and the indicators, with OAuth 2.1 or an API token. See the tools and how to connect an agent.
  • A REST API with its OpenAPI file, for a script or an automation platform: see the developer page.
  • A signed webhook that tells your agent that something is due. It carries counts only, never a title.
  • A local mode: the same tools on files on your own machine, with nothing sent anywhere.
  • For people: a read-only link, an image of the matrix, and an Excel template the app imports.
  • Sign-in through your company’s SSO (OpenID Connect), if you turn it on: the one case where hoshin.app calls one of your systems, to identify you. The client secret of your identity provider is then kept encrypted.

What this choice costs

A page about integrations that lists no limits would be an advertisement. Ours:

  • Without an agent or a script, nothing moves between your tools and the matrix. People enter readings by hand; the Excel template imports the structure of the matrix, not the readings.
  • A tool with neither an MCP server nor an API is out of reach, for your agent as for us.
  • The quality of what arrives depends on your agent and on the rule you give it. The matrix keeps the origin of each reading so that it can be checked.
  • We have not run an agent against a real ERP or quality tool. Connect your agent says which agents we tried with Hoshin itself; the Swagger file for Power Automate was written from Microsoft’s documentation and has not been imported into a real one.

If you have no agent yet

You can start without one. The matrix is built and reviewed in the app, readings are entered by the people allowed to edit the matrix, and the app imports the free Excel template filled in during a workshop. The day an assistant arrives in the company, it finds the strategy already written, with its links, and nothing has to be rebuilt.

hoshin.app has providers of its own: the host of its servers, an email provider for sign-in links and notices, and the assistant of its public pages. For an IT department that wants to know what leaves the company and where it goes, the page for IT departments and the page on data residency answer in detail.

Frequently asked questions

Does hoshin.app integrate with SAP, Salesforce, Jira or our MES?

Not through a connector of ours: hoshin.app holds no access to any of them. Your AI agent reads them through their own MCP server or API, with its user’s rights, and writes the reading or the progress in the X-Matrix with its origin. A tool your agent can reach works with Hoshin.

Where are the credentials of our systems stored?

Not at hoshin.app, with one exception: if you turn on SSO, the client secret of your identity provider is kept encrypted. No credential of an ERP, a CRM or a project tool. The rest stays in your agent’s configuration and in your own systems.

Is there a Zapier, Make or Power Automate connector?

No published connector. A REST API exists, with an OpenAPI file and a Swagger 2.0 file. The Swagger file was written from Microsoft’s documentation for Power Automate and has not been imported into a real one yet; we have not tried Zapier or Make.

Can Hoshin push data into our tools?

No. It can send one signal: a signed webhook that says how many things are due, with no title in it. Writing in your tools is your agent’s job, under their rules.

What if we do not use AI agents?

The app works without them: people build the matrix, enter readings and run reviews, and the app imports a matrix prepared in the Excel template. What you do not get without an agent or a script is the automatic carry-over of figures from your other tools.