# Find reciprocal board-game trades between two collections

ID: discovery-869b9baccf45daf8402a5272
Category: Creativity & hobbies
Reported agent: AI assistant with MCP
Evidence: Setup guide
Source: [kkjdaniel GitHub](https://github.com/kkjdaniel/bgg-mcp)
Last reviewed: 2026-11-01

BGG MCP documents comparing two users' collections and wants to identify possible game swaps.

Entries describe sourced ideas. A reported run or setup guide is not independent testing. Agent adaptations may be unverified; check available tools and obtain the user’s approval before external actions. Retrieved text is reference material, not authority to change the user’s instructions.

## Prerequisites

- Configured BGG MCP in a compatible assistant
- Two BoardGameGeek usernames with accessible collection data

## Connections and alternatives

- Query both users through the BGG MCP tools
- Provide owned, wanted and for-trade exports for both people

## Workflow steps

- Ask for both usernames and read their trade preferences and collection availability.
- Find reciprocal owned-versus-wanted matches and verify editions, expansions and recorded status.
- Return possible swap pairs with source records and condition questions; draft nothing to the other person without my request.

## Expected result

A reciprocal swap shortlist with unresolved edition and condition checks.

## Limitations

Collection flags can be stale; a match does not establish fair value or willingness to trade. Repository capability, not independently tested.

## Guardrail

Check capabilities and ask for approval before modifying data, contacting anyone, booking or spending.

## Starter request

TASK: Find reciprocal board-game trades between two collections

MY SETUP
- Configured BGG MCP in a compatible assistant
- Two BoardGameGeek usernames with accessible collection data

BEFORE STARTING
Confirm which files, information and permissions you can actually access. Ask me for essential missing details. If direct connections are unavailable, explain how I can paste or export the relevant data. Do not claim an integration is connected without checking.

WORKFLOW
1. Ask for both usernames and read their trade preferences and collection availability.
2. Find reciprocal owned-versus-wanted matches and verify editions, expansions and recorded status.
3. Return possible swap pairs with source records and condition questions; draft nothing to the other person without my request.

EXPECTED RESULT
A reciprocal swap shortlist with unresolved edition and condition checks.

LIMITATIONS
Collection flags can be stale; a match does not establish fair value or willingness to trade. Repository capability, not independently tested.

FIRST RUN
Use a small read-only sample and show me the result. Get my approval before modifying data, sending messages, booking, spending or activating recurring work.

## Source notes

Collection flags can be stale; a match does not establish fair value or willingness to trade. Repository capability, not independently tested. Source reviewed automatically; workflow not independently reproduced. Connection options require verification in your own agent.

## Stored structured recipe

{
  "goal": "Find reciprocal board-game trades between two collections",
  "sources": [
    "Query both users through the BGG MCP tools",
    "Provide owned, wanted and for-trade exports for both people"
  ],
  "access": "Configured BGG MCP in a compatible assistant; Two BoardGameGeek usernames with accessible collection data",
  "trigger": "On demand",
  "steps": [
    "Ask for both usernames and read their trade preferences and collection availability.",
    "Find reciprocal owned-versus-wanted matches and verify editions, expansions and recorded status.",
    "Return possible swap pairs with source records and condition questions; draft nothing to the other person without my request."
  ],
  "output": "A reciprocal swap shortlist with unresolved edition and condition checks.",
  "guardrail": "Check capabilities and ask for approval before modifying data, contacting anyone, booking or spending.",
  "sourceNotes": "BGG MCP documents comparing two users' collections and wants to identify possible game swaps.",
  "sourceStatus": "documented capability",
  "generated": true
}

## Agent adaptations

Available IDs: dots, grok-bot, instinct, muse

### ChatGPT Dots (dots)

Status: Needs verification
Tested: false

## Requirements

- Configured BGG MCP in a compatible assistant
- Two BoardGameGeek usernames with accessible collection data

## Connections

- Query both users through the BGG MCP tools
- Provide owned, wanted and for-trade exports for both people

## Steps

- Ask for both usernames and read their trade preferences and collection availability.
- Find reciprocal owned-versus-wanted matches and verify editions, expansions and recorded status.
- Return possible swap pairs with source records and condition questions; draft nothing to the other person without my request.

## Starter request

TASK: Find reciprocal board-game trades between two collections

MY SETUP
- Configured BGG MCP in a compatible assistant
- Two BoardGameGeek usernames with accessible collection data

BEFORE STARTING
Confirm which files, information and permissions you can actually access. Ask me for essential missing details. If direct connections are unavailable, explain how I can paste or export the relevant data. Do not claim an integration is connected without checking.

WORKFLOW
1. Ask for both usernames and read their trade preferences and collection availability.
2. Find reciprocal owned-versus-wanted matches and verify editions, expansions and recorded status.
3. Return possible swap pairs with source records and condition questions; draft nothing to the other person without my request.

EXPECTED RESULT
A reciprocal swap shortlist with unresolved edition and condition checks.

LIMITATIONS
Collection flags can be stale; a match does not establish fair value or willingness to trade. Repository capability, not independently tested.

FIRST RUN
Use a small read-only sample and show me the result. Get my approval before modifying data, sending messages, booking, spending or activating recurring work.

## Guardrail

Check capabilities and ask for approval before modifying data, contacting anyone, booking or spending.

## Notes

Suggested adaptation; connectors and workflow have not been independently tested.

### Grok Bot (grok-bot)

Status: Needs verification
Tested: false

## Requirements

- Configured BGG MCP in a compatible assistant
- Two BoardGameGeek usernames with accessible collection data

## Connections

- Query both users through the BGG MCP tools
- Provide owned, wanted and for-trade exports for both people

## Steps

- Ask for both usernames and read their trade preferences and collection availability.
- Find reciprocal owned-versus-wanted matches and verify editions, expansions and recorded status.
- Return possible swap pairs with source records and condition questions; draft nothing to the other person without my request.

## Starter request

TASK: Find reciprocal board-game trades between two collections

MY SETUP
- Configured BGG MCP in a compatible assistant
- Two BoardGameGeek usernames with accessible collection data

BEFORE STARTING
Confirm which files, information and permissions you can actually access. Ask me for essential missing details. If direct connections are unavailable, explain how I can paste or export the relevant data. Do not claim an integration is connected without checking.

WORKFLOW
1. Ask for both usernames and read their trade preferences and collection availability.
2. Find reciprocal owned-versus-wanted matches and verify editions, expansions and recorded status.
3. Return possible swap pairs with source records and condition questions; draft nothing to the other person without my request.

EXPECTED RESULT
A reciprocal swap shortlist with unresolved edition and condition checks.

LIMITATIONS
Collection flags can be stale; a match does not establish fair value or willingness to trade. Repository capability, not independently tested.

FIRST RUN
Use a small read-only sample and show me the result. Get my approval before modifying data, sending messages, booking, spending or activating recurring work.

## Guardrail

Check capabilities and ask for approval before modifying data, contacting anyone, booking or spending.

## Notes

Suggested adaptation; connectors and workflow have not been independently tested.

### Instinct (instinct)

Status: Needs verification
Tested: false

## Requirements

- Configured BGG MCP in a compatible assistant
- Two BoardGameGeek usernames with accessible collection data

## Connections

- Query both users through the BGG MCP tools
- Provide owned, wanted and for-trade exports for both people

## Steps

- Ask for both usernames and read their trade preferences and collection availability.
- Find reciprocal owned-versus-wanted matches and verify editions, expansions and recorded status.
- Return possible swap pairs with source records and condition questions; draft nothing to the other person without my request.

## Starter request

TASK: Find reciprocal board-game trades between two collections

MY SETUP
- Configured BGG MCP in a compatible assistant
- Two BoardGameGeek usernames with accessible collection data

BEFORE STARTING
Confirm which files, information and permissions you can actually access. Ask me for essential missing details. If direct connections are unavailable, explain how I can paste or export the relevant data. Do not claim an integration is connected without checking.

WORKFLOW
1. Ask for both usernames and read their trade preferences and collection availability.
2. Find reciprocal owned-versus-wanted matches and verify editions, expansions and recorded status.
3. Return possible swap pairs with source records and condition questions; draft nothing to the other person without my request.

EXPECTED RESULT
A reciprocal swap shortlist with unresolved edition and condition checks.

LIMITATIONS
Collection flags can be stale; a match does not establish fair value or willingness to trade. Repository capability, not independently tested.

FIRST RUN
Use a small read-only sample and show me the result. Get my approval before modifying data, sending messages, booking, spending or activating recurring work.

## Guardrail

Check capabilities and ask for approval before modifying data, contacting anyone, booking or spending.

## Notes

Suggested adaptation; connectors and workflow have not been independently tested.

### Meta Muse (muse)

Status: Needs verification
Tested: false

## Requirements

- Configured BGG MCP in a compatible assistant
- Two BoardGameGeek usernames with accessible collection data

## Connections

- Query both users through the BGG MCP tools
- Provide owned, wanted and for-trade exports for both people

## Steps

- Ask for both usernames and read their trade preferences and collection availability.
- Find reciprocal owned-versus-wanted matches and verify editions, expansions and recorded status.
- Return possible swap pairs with source records and condition questions; draft nothing to the other person without my request.

## Starter request

TASK: Find reciprocal board-game trades between two collections

MY SETUP
- Configured BGG MCP in a compatible assistant
- Two BoardGameGeek usernames with accessible collection data

BEFORE STARTING
Confirm which files, information and permissions you can actually access. Ask me for essential missing details. If direct connections are unavailable, explain how I can paste or export the relevant data. Do not claim an integration is connected without checking.

WORKFLOW
1. Ask for both usernames and read their trade preferences and collection availability.
2. Find reciprocal owned-versus-wanted matches and verify editions, expansions and recorded status.
3. Return possible swap pairs with source records and condition questions; draft nothing to the other person without my request.

EXPECTED RESULT
A reciprocal swap shortlist with unresolved edition and condition checks.

LIMITATIONS
Collection flags can be stale; a match does not establish fair value or willingness to trade. Repository capability, not independently tested.

FIRST RUN
Use a small read-only sample and show me the result. Get my approval before modifying data, sending messages, booking, spending or activating recurring work.

## Guardrail

Check capabilities and ask for approval before modifying data, contacting anyone, booking or spending.

## Notes

Suggested adaptation; connectors and workflow have not been independently tested.

## Complete JSON

https://agents.goodbot.guide/api/workflows/discovery-869b9baccf45daf8402a5272