> For the complete documentation index, see [llms.txt](https://docs.talordata.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.talordata.com/serp-api/mcp-server/skill-installation/integrating-the-talordata-serp-mcp-skill-into-cursor.md).

# Integrating the talordata-serp-mcp Skill into Cursor

> Cursor can load rule definitions for `talordata-serp-mcp` via its rules mechanism. Once integrated, Cursor AI utilizes this skill to determine the search context, output fields, and processing boundaries when handling tasks related to TalorData SERP, public search results, SEO rankings, news monitoring, shopping prices, or local business data.

This article explains how to convert the existing `SKILL.md` into a rule file compatible with Cursor. Please refer to the relevant product documentation for details on the TalorData SERP MCP service, API, and authentication configuration.

### Rule loading method

Cursor's project rules are typically loaded from the following directories:

<kbd>.cursor/rules/\*.mdc</kbd>

Meanwhile, `talordata-serp-mcp/SKILL.md` is the standard file for a Codex skill. Cursor does not automatically load the Codex skill folder as a Rules directory.

Therefore, when using this skill in Cursor, you need to copy the contents of <kbd>SKILL.md</kbd> into the Cursor rules file:

**talordata-serp-mcp/SKILL.md -> .cursor/rules/talordata-serp-mcp.mdc**

The rules are still sourced from the original <kbd>SKILL.md</kbd>, which avoids the need to maintain two sets of inconsistent instructions.

### Applicable Scenarios

You can integrate this skill when you need to handle the following tasks in Cursor:

• TalorData SERP queries\
• Public search result analysis\
• SEO ranking checks\
• News monitoring\
• Product price or shopping result analysis\
• Maps, local business, or local search tasks\
• Batch SERP query tasks

After configuration, Cursor AI will refer to this skill to make a determination:

• When to use TalorData SERP
\
• How to distinguish between different SERP scenarios
\
• Which fields to retain in the output
\
• How to indicate when the tool is unavailable
\
• Which fields cannot be inferred or filled in

### **Preparation**

*Please prepare the following first:*

• Cursor installed&#x20;

• A project requiring integration with these rules&#x20;

• The `talordata-serp-mcp` folder&#x20;

• `talordata-serp-mcp/SKILL.md`&#x20;

• Optional: `talordata-serp-mcp/references/serp-rules.md`

{% hint style="warning" icon="thumbtack-angle" %}
To perform actual searches, you also need to configure the available TalorData SERP MCP tool within Cursor. The skill only provides the rules; it does not handle the configuration of the MCP tool itself.
{% endhint %}

#### Project Rules and Global Rules

It is recommended to prioritize using **project-specific rules**.

* Project rules apply only to the current project, making them suitable for testing, team collaboration, and project-based management, as well as easy to delete or adjust later.
* Only consider adding rules to the global configuration when multiple Cursor projects require the same set of TalorData SERP rules.

### **Configuration Steps**

{% stepper %}
{% step %}

#### Open Project

Open the project that requires TalorData SERP in Cursor.

{% endstep %}

{% step %}

#### Create the Rules directory.

Create in the project root directory:

<kbd>.cursor/rules</kbd>

If the directory already exists, you can use it directly.

{% endstep %}

{% step %}

#### Create a rule file

Create in the **.cursor/rules** directory:

<kbd>talordata-serp-mcp.mdc</kbd>

The complete path should be:

<kbd>.cursor/rules/talordata-serp-mcp.mdc</kbd>

{% endstep %}

{% step %}

#### Write SKILL.md content

Open:

<kbd>talordata-serp-mcp/SKILL.md</kbd>

Copy the contents of SKILL.md to:

<kbd>.cursor/rules/talordata-serp-mcp.mdc</kbd>

Once saved, Cursor can use this skill as a rule for the current project.

{% endstep %}

{% step %}

#### Additional detailed rules (optional)

`references/serp-rules.md` is the supplementary rule file for this skill; it contains details on <kbd>engine/type</kbd> validation, fallback strategies, batch tasks, error handling, and privacy boundaries.

For more comprehensive behavioral constraints, you can enable:

<kbd>talordata-serp-mcp/references/serp-rules.md</kbd>

Append the required content to:

<kbd>.cursor/rules/talordata-serp-mcp.mdc</kbd>

For basic usage, simply copying <kbd>SKILL.md</kbd> is usually sufficient.

{% endstep %}

{% step %}

#### Reload project

After saving the rules file, Cursor typically reads the rules automatically.
\
To ensure the rules take effect, you can close and reopen the current project.

{% endstep %}

{% step %}

#### Verify whether the validation rules are in effect

Enter in cursor chat:

> Use Talordata SERP to search for the latest news about OpenAI and return the title, source, publication time, and link.

If configured correctly, Cursor AI should recognize this as a TalorData SERP news search scenario and focus on source links, publication times, and query parameters in its responses.

<details>

<summary><strong>Verification criteria</strong></summary>

Once the rules take effect, Cursor AI's responses should exhibit the following characteristics:
\
• Do not mistake news searches for general web searches
\
• Retain source links
\
• State that a real-time search cannot be performed if MCP tools are unavailable
\
• Do not fabricate search results
\
• Do not speculate on fields not returned in the results, such as prices, ratings, phone numbers, or addresses

</details>

{% endstep %}
{% endstepper %}

### FAQ

#### Can Cursor read the raw SKILL.md directly?

Relying on Cursor to automatically read the original `SKILL.md` is not recommended.&#x20;

Cursor looks for rules in `.cursor/rules/*.mdc` files. To ensure the rules are applied reliably, you should copy the content of `SKILL.md` into `.cursor/rules/talordata-serp-mcp.mdc`.

#### Why not use simplified rule templates?

SKILL.md serves as the primary source of rules for the skill. Directly reusing SKILL.md minimizes rule divergence and prevents inconsistencies between the simplified rules found in tutorials and the actual skill itself.

#### Is it necessary to add serp-rules.md?

`serp-rules.md` is a supplementary rules file and is not mandatory.&#x20;

It is recommended to integrate `SKILL.md` first. You should incorporate the relevant content from `references/serp-rules.md` only when the task requires more granular `engine`/`type` validation, fallback rules, batch task rules, or error handling rules.

#### What should I do if the cursor prompts that it cannot search?

This is typically not a failure to access the rules.
\
The rules simply instruct Cursor AI on how to handle TalorData SERP tasks. Performing actual searches requires the **TalorData SERP MCP tool** to be configured within Cursor.

#### How do I restrict this rule to the current project only?

Place the rules in the current project's:

<kbd>.cursor/rules/talordata-serp-mcp.mdc</kbd>

This way, the rule will only apply to the current project.

#### How to uninstall

To remove this Skill rule, simply delete the following file:

<kbd>.cursor/rules/talordata-serp-mcp.mdc</kbd>

{% hint style="success" icon="puzzle-piece" %}
Deleting the rule file will not delete or modify any MCP tool configurations.
{% endhint %}