2,500+ MCP servers ready to use
Vinkius

OneSignal 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 OneSignal as an MCP tool provider through the 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 OneSignal. "
            "You have 10 tools available."
        ),
    )

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

asyncio.run(main())
OneSignal
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 OneSignal MCP Server

Connect your OneSignal account to any AI agent and take full control of your customer engagement workflows through natural conversation.

LlamaIndex agents combine OneSignal tool responses with indexed documents for comprehensive, grounded answers. Connect 10 tools through the 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

  • Notifications Management — Send, schedule, and cancel push notifications across mobile and web platforms.
  • Audience Targeting — Target specific segments or individual player IDs to ensure the right message reaches the right user.
  • Delivery Analytics — Fetch detailed reports and metrics for any notification to understand your engagement levels.
  • Device Management — List, inspect, and manage registered devices (players) within your OneSignal applications.
  • App Overview — List all your OneSignal apps and configurations to maintain a bird's-eye view of your notification infrastructure.

The OneSignal 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 OneSignal to LlamaIndex via MCP

Follow these steps to integrate the OneSignal 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 OneSignal

Why Use LlamaIndex with the OneSignal MCP Server

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

01

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

02

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

03

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

04

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

OneSignal + LlamaIndex Use Cases

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

01

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

02

Data enrichment: query OneSignal 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 OneSignal for fresh data

04

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

OneSignal MCP Tools for LlamaIndex (10)

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

01

cancel_notification

Cancel a scheduled notification

02

create_notification

Send a OneSignal notification

03

delete_player

Delete a registered device

04

get_app

Requires User Auth Key. Get details for a specific OneSignal app

05

get_notification

Get specific notification status

06

get_outcomes

Get outcome data for the app

07

get_player

Get specific player details

08

list_apps

Requires User Auth Key. List all OneSignal apps

09

list_notifications

List notifications sent for the app

10

list_players

List registered devices (players)

Example Prompts for OneSignal in LlamaIndex

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

01

"Send a push notification to all subscribed users saying 'Flash Sale: 50% off today only!'"

02

"Check the delivery status of notification 550e8400-e29b-41d4-a716-446655440000."

03

"List the last 5 registered devices for our app."

Troubleshooting OneSignal MCP Server with LlamaIndex

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

01

BasicMCPClient not found

Install: pip install llama-index-tools-mcp

OneSignal + LlamaIndex FAQ

Common questions about integrating OneSignal 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 OneSignal 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 OneSignal to LlamaIndex

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