Advanced: programmatic access¶
Connecting MarketBuddy to n8n, Make, custom scripts, or your own apps.
The interactive sign-in flow used by Claude, ChatGPT, and Cursor is convenient but it requires a browser. If you want to call MarketBuddy from automated workflows or your own code, you can authenticate with a MarketBuddy API token instead.
Same data, different auth
Both authentication methods give access to the same MarketBuddy MCP tools and data. The only difference is how you sign in.
Get an API token¶
API tokens aren't yet self-serve. To request one, contact our team via the Support Portal and tell us roughly what you're building (n8n flow, internal script, etc.) so we can issue a token for your account.
Tokens start with pdj_ - treat them like a password. They don't expire by default, but we can revoke or time-limit a token on request.
Server details¶
- MCP endpoint:
https://mcp.marketbuddy.com.au/mcp - Transport: Streamable HTTP
- Auth header:
Authorization: Bearer pdj_<your-token>
Connect from n8n or Make¶
In an MCP-aware node:
- Server URL:
https://mcp.marketbuddy.com.au/mcp - Authentication: Bearer token
- Token: your
pdj_…value
No OAuth flow is required - the bearer token is checked on every request.
Connect from a custom client¶
Any MCP client that supports streamable HTTP and a custom Authorization header can connect. The MarketBuddy server exposes three tools - faceted_search, radial_search, and property_details. See Supported tools for what each one does.
Health check¶
Returns {"status": "ok", "version": "..."}. No authentication required.
Need raw HTTP examples or schema definitions?¶
For full request/response examples and JSON schemas, contact our team via the Support Portal - we'll point you at the latest reference.