Integration
Connect Cursor to Wikipedia Search API
When Agent Pull Request Created fires in Cursor, your agent runs Geosearch (Pages Near Coordinates) in Wikipedia Search API. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Cursor and Wikipedia Search API to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What Cursor can start in Wikipedia Search API
When Agent Pull Request Created in Cursor
then Geosearch (Pages Near Coordinates) in Wikipedia Search API
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with Cursor and Wikipedia Search API
Triggers and actions 3 triggers · 30 actions
- Agent Pull Request Created
Triggers when the selected Cursor cloud agent opens a new GitHub pull request.
- Agent Status Equals
Triggers when a run on the chosen Cursor agent reaches the status you select, such as Finished or Error.
- New Agent
Triggered when a new Cursor cloud agent is created.
- Add Followup Instruction to Agent
Sends a follow-up instruction to an existing Cursor cloud agent, either starting a new run or steering the run in progress. Returns the new run or how the steer was delivered.
- Cancel run
Cancels the active run of a Cursor cloud agent. The run ends in the Cancelled state; start a new run to continue the conversation.
- Delete Agent
Permanently deletes a Cursor cloud agent. This cannot be undone. Returns the ID of the deleted agent.
- Find Agent Status
Looks up a Cursor cloud agent by its ID and returns its status, name, repositories, latest run and link.
- Get run
Returns the status, timestamps, duration, final reply and pushed branches for one run of a Cursor cloud agent.
- Launch Agent
Creates a Cursor cloud agent and immediately starts its first run on the task you describe. Returns the new agent and its run.
- List agents
Returns the Cursor cloud agents for the connected user, newest first, optionally filtered by pull request URL.
- List artifacts
Returns the files a Cursor cloud agent has produced, with each file's path, size and last modified time. Returns at most 100 artifacts.
- List models
Returns the recommended Cursor models you can choose from when creating an agent, including their names, aliases, parameters and variants.
- List repositories
Returns the GitHub repositories the connected Cursor user can access through Cursor's GitHub App installation.
- List runs
Returns the runs of a Cursor cloud agent, newest first, including each run's status, duration, and final reply.
- Geosearch (Pages Near Coordinates)
Find Wikipedia pages located near a geographic coordinate, within a given radius.
- Get Backlinks (What Links Here)
Get the list of Wikipedia pages that link TO a given page.
- Get Category Members
List the pages and subcategories that are members of a given Wikipedia category.
- Get External Links
Get the list of external (off-wiki) URLs referenced on a Wikipedia page.
- Get Featured Content
Get Wikipedia's featured content for a date: the featured article, most-read articles, picture of the day, and news, via the REST feed API.
- Get Page Categories
Get the categories a Wikipedia page belongs to.
- Get Page Content (Plain Text)
Get the full plain-text extract of a Wikipedia page (optionally intro-only) via the MediaWiki Action API.
- Get Page Coordinates
Get the geographic coordinates (latitude/longitude) associated with a Wikipedia page.
- Get Page HTML
Get the rendered HTML of a Wikipedia page via the REST API.
- Get Page Images
Get the list of image file titles used on a Wikipedia page.
- Get Page Info
Get metadata about a Wikipedia page: page ID, last-modified timestamp, length, protection, content model, and full URL.
- Get Page Links
Get the list of internal wiki links (outgoing links to other pages) from a Wikipedia page.
- Get Page Revisions
Get the revision history of a Wikipedia page: revision IDs, timestamps, editors, and comments.
- Get Page Sections
Get the section structure (headings and table of contents) of a Wikipedia page via the parse API.
- Get Page Summary
Get a concise summary of a Wikipedia page (extract, thumbnail, description, and canonical URL) via the REST API.
- Get Random Pages
Get one or more random Wikipedia article titles.
- On This Day
Get notable historical events, births, deaths, and holidays for a given month and day via the REST feed API.
- Search Pages
Full-text search of Wikipedia pages. Returns matching page titles, snippets, page IDs, word counts, and timestamps.
- Search Titles (Autocomplete)
Prefix/autocomplete search over page titles using the OpenSearch protocol. Returns matching titles, descriptions, and URLs.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Cursor
Cursor to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Cursor to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Cursor to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Cursor to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Cursor to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Cursor to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Wikipedia Search API
Questions
Cursor and Wikipedia Search API, answered
What can start an automation from Cursor?
Any of Cursor's 3 triggers in the catalog, including Agent Pull Request Created, New Agent and Agent Status Equals. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Wikipedia Search API when something happens in Cursor?
Any of Wikipedia Search API's 19 actions, including Geosearch (Pages Near Coordinates), Get Backlinks (What Links Here), Get Category Members and Get External Links. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Wikipedia Search API to Cursor?
Wikipedia Search API has no triggers in the catalog today, so automations start in Cursor. If you need the other direction, ask: your agent reads Wikipedia Search API's API documentation and adds it.
Do I have to build a connector for Cursor or Wikipedia Search API?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
Can my AI client use Cursor and Wikipedia Search API without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.