Skip to main content
Glama
ASX Announcements MCP Server

ASX Announcements MCP Server

by pipeworx-io
README.md
# @pipeworx/asx-announcements

ASX company announcements for Australian listed companies, with a share-issue / dilution view and company details. Read live from the exchange per request.

Part of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1875+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

## Tools

- `asx_get_announcements(ticker, months?, year?, price_sensitive_only?, category?, limit?)` - announcements newest first: date and time (Sydney), headline, price-sensitive flag, pages, file size, a derived category and a document link. Categories: share_issue, unquoted_securities, cessation_of_securities, buyback, director_interest, substantial_holder, trading_halt, quarterly_cashflow, results, meeting, other.
- `asx_get_share_issues(ticker, months?, year?)` - only the announcements that signal new or changed share capital (Appendix 2A quotation applications, Appendix 3B proposed issues, placements, share purchase plans, entitlement offers, options and performance rights, cessations, buy-backs), with counts per category and per month.
- `asx_get_company(ticker)` - name, description, listing date, sector, directors, registry, shares on issue, market cap, price range, dividend and headline financials.

## Auth

Keyless.

## Data sources

- ASX (Australian Securities Exchange), company announcements - the public, delayed announcements feed per company.
- ASX (Australian Securities Exchange), company information - the public company profile and key statistics.

Notes for the next person:

- A window is a rolling 1, 3 or 6 months, or one full calendar year. The announcements list for a window is complete; there is no row cap on the source side.
- Categories are derived from ASX's own headline text, not from the PDF. Share counts and issue prices are inside the linked document and are not extracted.
- An unknown ticker is reported as an error, not an empty list. A valid ticker with nothing in the window returns zero rows with a note saying so.
- Times are Sydney local time as shown by ASX.

## Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

```json
{
  "mcpServers": {
    "asx-announcements": {
      "url": "https://gateway.pipeworx.io/asx-announcements/mcp"
    }
  }
}
```

### What this endpoint actually serves

`tools/list` at `https://gateway.pipeworx.io/asx-announcements/mcp` returns the tools in the table
above **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,
`discover_tools`, `search_within`, `remember`/`recall` and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's `initialize` response states its exact scope, and
is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
`ask_pipeworx`, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed
directly, instead of just this one's:

```json
{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}
```

Both URLs reach the same gateway and the same 1875+ data sources. The
only difference is which pack's tools are listed **directly**; `ask_pipeworx`
reaches all of them from either one.

## No MCP client? Call it over HTTP

```bash
curl -X POST https://gateway.pipeworx.io/v1/tools/asx_get_announcements \
  -H 'Content-Type: application/json' \
  -d '{"ticker":"LTR","months":6,"limit":10}'
```

No account needed for the first calls. Inspect any tool: `GET https://gateway.pipeworx.io/v1/tools/asx_get_announcements`. Find one: `POST https://gateway.pipeworx.io/v1/tools/search_packs` with `{"query":"..."}`.

## Run it from npm

`@pipeworx/mcp-asx-announcements` is a local stdio bridge to the Pipeworx gateway: your MCP client
starts it with `npx`, and it forwards every call to the same
`https://gateway.pipeworx.io/asx-announcements/mcp` endpoint shown above. It needs network access;
there is no offline mode.

```json
{
  "mcpServers": {
    "asx-announcements": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-asx-announcements"]
    }
  }
}
```

Without a key it calls anonymously, capped at 50 calls a day. A free account
raises that to 200 a day: get a key at https://pipeworx.io/signup and add
`"env": { "PIPEWORX_API_KEY": "<your key>" }` to the server entry.
The key is sent as a Bearer token, the same way a hosted connection sends it,
so calls are metered and billed exactly as they are there.

It lists **only** this pack's tools by default. Set `PIPEWORX_META_TOOLS=1` to
also list `ask_pipeworx` and the other gateway-wide tools.

Behind an HTTPS proxy: Node's built-in `fetch` does not read `HTTPS_PROXY` by
default. Newer Node releases honour it when `NODE_USE_ENV_PROXY=1` is set; check
your Node version's documentation.

## Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English —
this works on the pack endpoint above as well as on the full gateway:

```
ask_pipeworx({ question: "your question about Asx Announcements data" })
```

The gateway picks the right tool and fills the arguments automatically.

## More

- [Docs and guides](https://pipeworx.io/docs)
- [pipeworx.io](https://pipeworx.io)

## License

MIT