Quick answer
Use WorkBuddy with FXMacroData by connecting the hosted MCP server at https://mcp.fxmacrodata.com/mcp, or by adding a focused REST-backed skill for one controlled data request. Start with a public USD test, add an FXMacroData API key for protected tools, and require WorkBuddy to cite the FXMacroData endpoint before it writes an FX macro brief.
WorkBuddy is Tencent Cloud's desktop AI agent workbench for business workflows such as research, data analysis, coding, and report generation. FXMacroData supplies the current macro evidence layer: release calendars, announcement history, policy rates, inflation, GDP, labor data, FX sessions, COT positioning, commodities, and hosted MCP tools.
The useful boundary is simple. WorkBuddy can coordinate the task and write the briefing. FXMacroData should answer the factual market questions: what was released, what was prior, what is scheduled, what data is available, and which FXMacroData endpoint supports the answer. That keeps a prompt about USD/JPY, US CPI, or the release calendar tied to current data instead of model memory.
Good fit
Analysts, developers, and small teams using WorkBuddy for macro research, event-risk notes, data checks, and report drafting.
Use MCP when
Your WorkBuddy workspace supports MCP or CodeBuddy-style MCP configuration and should discover hosted FXMacroData tools.
Use REST when
You want one explicit endpoint, one reviewed request shape, and direct control over credential storage.
What WorkBuddy Adds
Tencent Cloud describes WorkBuddy as a full-scenario AI agent desktop workstation with per-task model configuration, local file operations, and connections to office and collaboration tools. Its guides describe a Skill Marketplace and custom Skills as the extension points; MCP connector support varies by edition and connector screen, so confirm it in your own workspace before relying on it. That makes WorkBuddy a natural place to run repeatable research workflows where the assistant needs current external data.
FXMacroData is not the model and it is not the reasoning layer. It is the evidence service. When WorkBuddy asks a market question, FXMacroData can return the rows and metadata that ground the answer: release timestamps, actual values, prior values, calendars, supported indicators, FX context, and endpoints a human can inspect.
1. Ask
Request a release brief, calendar check, pair setup, or macro evidence pull.
2. Retrieve
WorkBuddy calls FXMacroData through MCP or a REST-backed skill.
3. Explain
The assistant writes a brief using returned rows and named unknowns.
4. Review
A human checks the evidence before it enters a trading workflow.
Choose MCP, REST, or a WorkBuddy Skill
| Surface | Use it when | Why it matters |
|---|---|---|
| FXMacroData MCP | Your WorkBuddy workspace should discover hosted macro tools from one server. | Best first path when MCP connectors are available. |
| FXMacroData REST | You need one explicit data request with a stable URL and schema. | Simple to test, easy to log, and good for a focused WorkBuddy skill. |
| WorkBuddy skill | Your WorkBuddy workspace supports skills but not remote MCP connectors. | Wrap a small REST request and return evidence-backed JSON to the assistant. |
| No connected data tools | You are writing a template or checklist without live data access. | Use only for structure and wording. Do not ask the model to invent current macro data. |
Prerequisites
- WorkBuddy installed and configured with an approved model. Tencent's setup guide shows the custom model flow from the WorkBuddy conversation page.
- An FXMacroData account if you need protected tools. A public USD check is enough for the first connection test.
- A secure setting for credentials, such as a WorkBuddy secret field or server environment variable.
- A read-only research boundary. Do not expose order routing, position sizing, or risk-changing tools to the assistant.
Setup checklist
- Open WorkBuddy and confirm your model can answer a normal message.
- Find the MCP, skills, plugins, or connector area in your WorkBuddy workspace.
- Add FXMacroData as a read-only data source.
- Run a public USD test question before adding protected credentials.
- Move to authenticated access only after the basic tool call works.
Step 1: Connect FXMacroData MCP
The hosted FXMacroData MCP server is available at:
https://mcp.fxmacrodata.com/mcpUse that public URL first to confirm the connection and run limited USD testing. For protected access, use your FXMacroData API key. If WorkBuddy asks for fields instead of JSON, use these values:
| Field | Value |
|---|---|
| Name | FXMacroData |
| Transport | HTTP or Streamable HTTP |
| Public URL | https://mcp.fxmacrodata.com/mcp |
| Authentication header | Authorization: Bearer YOUR_API_KEY (if the form only accepts a URL, use https://mcp.fxmacrodata.com/mcp?api_key=YOUR_API_KEY as a fallback) |
| Permission | Read-only macro data, calendars, FX context, and charts. |
If your WorkBuddy workspace uses CodeBuddy-style MCP JSON, a minimal entry looks like this:
{
"mcpServers": {
"fxmacrodata": {
"type": "http",
"url": "https://mcp.fxmacrodata.com/mcp",
"headers": {"Authorization": "Bearer ${FXMD_API_KEY}"}
}
}
}Prefer an environment variable or secret field if the client supports it. Do not paste a real API key into a shared prompt, screenshot, support ticket, or document. If your WorkBuddy workspace does not expose MCP connectors directly, use the REST fallback below or a WorkBuddy skill that calls the same endpoint family.
Step 2: Add a REST Fallback
REST is the right fallback when the workflow only needs one narrow request. For example, a WorkBuddy skill can retrieve recent Federal Reserve policy-rate announcements through the production FXMacroData API:
curl -H "X-API-Key: YOUR_API_KEY" "https://api.fxmacrodata.com/v1/announcements/usd/policy_rate"For a WorkBuddy skill or backend helper, keep the credential outside the prompt and return a compact object that includes the endpoint. The assistant can then summarize the result without seeing the API key.
const url = new URL("https://api.fxmacrodata.com/v1/announcements/usd/policy_rate");
const response = await fetch(url, {
headers: { "X-API-Key": process.env.FXMD_API_KEY },
});
const payload = await response.json();
return {
endpoint: "/v1/announcements/usd/policy_rate",
payload
};Use separate skills for separate jobs. A policy-rate lookup is easier to review than a generic web-fetching skill. Add more only when there is a real workflow, such as release-calendar review, CPI history, COT positioning, FX sessions, or commodities context.
Step 3: Test Research Prompts
Strong prompts make WorkBuddy retrieve data before writing commentary. Start with small checks:
Research prompt examples
- Calendar: "Use FXMacroData to list the next USD macro releases. Include the FXMacroData endpoint or data source used."
- Announcement history: "Get recent USD policy-rate announcements and summarize what changed. Separate data rows from interpretation."
- Pair context: "Prepare a USD/JPY event-risk note. Use FXMacroData for release timing and current session context before writing."
- Data availability: "Check whether FXMacroData has recent EUR inflation data. If a field is unavailable, say so explicitly."
Then inspect the answer. A useful WorkBuddy output should include the indicator, currency, retrieved date or schedule, FXMacroData endpoint, any data gaps, and a short interpretation. If the response jumps straight to a market view without evidence, ask for the data source and endpoint first.
Step 4: Add Finance Guardrails
WorkBuddy can speed up research drafting, but it should not become an unchecked trading system. Keep the connected surface read-only and make final output reviewable.
| Guardrail | Practical rule |
|---|---|
| Credentials | Store API keys in configuration or environment variables, not prompts. |
| Tool scope | Expose macro data reads only. Do not expose execution, brokerage, or risk-change tools. |
| Evidence | Require endpoints and data rows before any current-market claim. |
| Unknowns | Require the assistant to state missing, stale, or unavailable data. |
| Review | Route market conclusions through a human reviewer or documented review rule before action. |
Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| MCP server does not appear. | Your WorkBuddy workspace may not have MCP connectors enabled. | Use the REST fallback or a WorkBuddy skill, and check WorkBuddy or CodeBuddy MCP documentation for your exact interface. |
| Tool works for USD but not non-USD data. | The request needs authenticated FXMacroData access. | Add an API key or OAuth-backed access and retest with the key configured on the MCP connection. |
| The assistant gives a confident answer without evidence. | The prompt does not require tool use, or the tool was unavailable. | Ask it to call FXMacroData first and show the data source before interpretation. |
| Credential appears in a response. | The key was pasted into a prompt or visible config field. | Rotate the key and move it into a secret or environment variable. |
Related FXMacroData guides
Sources and references
