2,500+ MCP servers ready to use
Vinkius

ContentKing MCP Server for LlamaIndex 10 tools — connect in under 2 minutes

Built by Vinkius GDPR 10 Tools Framework

LlamaIndex specializes in data-aware AI agents that connect LLMs to structured and unstructured sources. Add ContentKing as an MCP tool provider through Vinkius and your agents can query, analyze, and act on live data alongside your existing indexes.

Vinkius supports streamable HTTP and SSE.

python
import asyncio
from llama_index.tools.mcp import BasicMCPClient, McpToolSpec
from llama_index.core.agent.workflow import FunctionAgent
from llama_index.llms.openai import OpenAI

async def main():
    # Your Vinkius token. get it at cloud.vinkius.com
    mcp_client = BasicMCPClient("https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp")
    mcp_tool_spec = McpToolSpec(client=mcp_client)
    tools = await mcp_tool_spec.to_tool_list_async()

    agent = FunctionAgent(
        tools=tools,
        llm=OpenAI(model="gpt-4o"),
        system_prompt=(
            "You are an assistant with access to ContentKing. "
            "You have 10 tools available."
        ),
    )

    response = await agent.run(
        "What tools are available in ContentKing?"
    )
    print(response)

asyncio.run(main())
ContentKing
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About ContentKing MCP Server

Integrate your AI with ContentKing, the real-time SEO auditing and monitoring platform.

LlamaIndex agents combine ContentKing tool responses with indexed documents for comprehensive, grounded answers. Connect 10 tools through Vinkius and query live data alongside vector stores and SQL databases in a single turn. ideal for hybrid search, data enrichment, and analytical workflows.

What you can do

  • Site Audits — Review crawled pages and identify active SEO risks or technical errors instantly.
  • Change Monitoring — Get summaries of recent alerts or infrastructure changes impacting SEO.
  • Metric Retrieval — Fetch health scores and page-level data for your reporting workflows.

The ContentKing MCP Server exposes 10 tools through the Vinkius. Connect it to LlamaIndex in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect ContentKing to LlamaIndex via MCP

Follow these steps to integrate the ContentKing MCP Server with LlamaIndex.

01

Install dependencies

Run pip install llama-index-tools-mcp llama-index-llms-openai

02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token

03

Run the agent

Save to agent.py and run: python agent.py

04

Explore tools

The agent discovers 10 tools from ContentKing

Why Use LlamaIndex with the ContentKing MCP Server

LlamaIndex provides unique advantages when paired with ContentKing through the Model Context Protocol.

01

Data-first architecture: LlamaIndex agents combine ContentKing tool responses with indexed documents for comprehensive, grounded answers

02

Query pipeline framework lets you chain ContentKing tool calls with transformations, filters, and re-rankers in a typed pipeline

03

Multi-source reasoning: agents can query ContentKing, a vector store, and a SQL database in a single turn and synthesize results

04

Observability integrations show exactly what ContentKing tools were called, what data was returned, and how it influenced the final answer

ContentKing + LlamaIndex Use Cases

Practical scenarios where LlamaIndex combined with the ContentKing MCP Server delivers measurable value.

01

Hybrid search: combine ContentKing real-time data with embedded document indexes for answers that are both current and comprehensive

02

Data enrichment: query ContentKing to augment indexed data with live information before generating user-facing responses

03

Knowledge base agents: build agents that maintain and update knowledge bases by periodically querying ContentKing for fresh data

04

Analytical workflows: chain ContentKing queries with LlamaIndex's data connectors to build multi-source analytical reports

ContentKing MCP Tools for LlamaIndex (10)

These 10 tools become available when you connect ContentKing to LlamaIndex via MCP:

01

get_active_alerts

Get active monitoring alerts for a website

02

get_issue_details

Get details for a specific SEO issue

03

get_portfolio_summary

Get a high-level health summary across all websites

04

get_website_health

Get current health score and status for a website

05

list_monitored_pages

List monitoring data for pages on a website

06

list_seo_issues

List SEO issues for a website

07

list_websites

List all websites monitored in ContentKing

08

notify_page_update

Notify ContentKing of page updates to trigger re-crawl

09

notify_sitemap_update

Notify ContentKing that a sitemap has been updated

10

search_pages_by_url

Search for monitored pages by URL keyword

Example Prompts for ContentKing in LlamaIndex

Ready-to-use prompts you can give your LlamaIndex agent to start working with ContentKing immediately.

01

"Get the current health score for 'vinkius.com'."

02

"List all critical alerts for meta tag changes today."

03

"Give me a high-level summary of the health of all my monitored websites."

Troubleshooting ContentKing MCP Server with LlamaIndex

Common issues when connecting ContentKing to LlamaIndex through the Vinkius, and how to resolve them.

01

BasicMCPClient not found

Install: pip install llama-index-tools-mcp

ContentKing + LlamaIndex FAQ

Common questions about integrating ContentKing MCP Server with LlamaIndex.

01

How does LlamaIndex connect to MCP servers?

Use the MCP client adapter to create a connection. LlamaIndex discovers all tools and wraps them as query engine tools compatible with any LlamaIndex agent.
02

Can I combine MCP tools with vector stores?

Yes. LlamaIndex agents can query ContentKing tools and vector store indexes in the same turn, combining real-time and embedded data for grounded responses.
03

Does LlamaIndex support async MCP calls?

Yes. LlamaIndex's async agent framework supports concurrent MCP tool calls for high-throughput data processing pipelines.

Connect ContentKing to LlamaIndex

Get your token, paste the configuration, and start using 10 tools in under 2 minutes. No API key management needed.