GEOly MCP
GEOly MCP Challenge
Found a question that GEOly MCP answers well? Write it up and send it in. Accepted entries are published in the use-case library as Community Built, credited to you.
What to build
- A question you paste into Claude, ChatGPT, Cursor or another MCP client connected to GEOly, that gets a useful answer from GEOly data
- Or a short multi-step workflow: a chain of follow-up questions that ends in something a team can act on
- It should solve a real job, such as a weekly check, a pitch, a fix list or an analysis, and be different from the use cases already in the library
Not sure which tools exist? See the full list in the docs. MCP docs
Rules
- Use only GEOly MCP tools that are in the public tool list. Name the tools your AI called.
- Work with your own brand data or GEOly public category data. Do not submit other people’s private data.
- Remove anything sensitive before you send it: client names you are not allowed to share, tokens and API keys.
- Describe what GEOly actually returned. Do not claim coverage of AI engines that GEOly does not monitor.
- Write in English or Chinese. One use case per submission; you can send several.
- It must be your own work. By submitting, you allow GEOly to edit it for length and clarity and publish it on geoly.ai in English and Chinese.
How to submit
Send your entry through the contact form or by email. Include:
- A title and who it is for
- The exact question (or questions) to paste
- The GEOly MCP tools your AI called
- What came back, and what you did with it; a redacted screenshot helps
- The name and link (website, GitHub, LinkedIn or X) you want on the page
Email: [email protected] · Subject: “GEOly MCP Challenge submission”
How entries get featured
- The GEOly team reads every entry and reruns the question on GEOly MCP to check it works as described.
- Accepted entries are written up in the same format as the other use cases and published under Community Built, in English and Chinese.
- Your name and link appear on the use case. We will contact you before publishing.
- Entries that duplicate an existing use case, or that we cannot reproduce, are not published. We will tell you why.