How to integrate Here MCP with Mastra AI

BOOK A CALLGET STARTED FOR FREE
Framework Integration Gradient
Here Logo
Mastra AI Logo
divider

Introduction

This guide walks you through connecting Here to Mastra AI using the Composio tool router. By the end, you'll have a working Here agent that can find coffee shops near central park, get driving route for delivery truck, convert address to latitude and longitude, show hybrid map tile for times square through natural language commands.

This guide will help you understand how to give your Mastra AI agent real control over a Here account through Composio's Here MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

TL;DR

Here's what you'll learn:
  • Set up your environment so Mastra, OpenAI, and Composio work together
  • Create a Tool Router session in Composio that exposes Here tools
  • Connect Mastra's MCP client to the Composio generated MCP URL
  • Fetch Here tool definitions and attach them as a toolset
  • Build a Mastra agent that can reason, call tools, and return structured results
  • Run an interactive CLI where you can chat with your Here agent

What is Mastra AI?

Mastra AI is a TypeScript framework for building AI agents with tool support. It provides a clean API for creating agents that can use external services through MCP.

Key features include:

  • MCP Client: Built-in support for Model Context Protocol servers
  • Toolsets: Organize tools into logical groups
  • Step Callbacks: Monitor and debug agent execution
  • OpenAI Integration: Works with OpenAI models via @ai-sdk/openai

What is the Here MCP server, and what's possible with it?

The Here MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Here account. It provides structured and secure access to powerful location, mapping, and geocoding services, so your agent can perform actions like searching places, calculating routes, fetching map imagery, and converting addresses or coordinates on your behalf.

  • Smart place discovery and suggestions: Ask your agent to find points of interest, get autosuggested places based on partial queries, or discover addresses near a location.
  • Geocoding and reverse geocoding: Convert addresses to geographic coordinates or vice versa, enabling seamless location lookup and mapping in your workflows.
  • Map tile and imagery retrieval: Direct your agent to fetch satellite, base, or hybrid map tiles for specific locations, zoom levels, and formats for rich visual context.
  • Advanced routing and fleet planning: Have your agent calculate optimized routes with vehicle profiles, constraints, and even isolines for reachable areas based on time or distance.
  • Nearby search and contextual browsing: Let your agent browse or search for places around a given location, filtered by categories or names, to surface relevant local information.

Supported Tools & Triggers

Tools
Autosuggest PlacesTool to fetch possible completions for a partial search term.
Browse PlacesTool to search for places around a given location with optional filters.
Calculate Fleet Telematics RouteTool to calculate a route between waypoints with vehicle profile options.
Coordinates to Tile IndicesTool to convert geographic coordinates to Web Mercator XYZ tile indices.
Discover PlacesTool to discover places and addresses by free-form text near a location.
Geocode AddressTool to convert structured address data into geographic coordinates.
Get Aerial TileTool to retrieve a satellite/aerial map tile.
Get Base Map TileTool to retrieve a base map tile image without labels.
Get Hybrid Map TileTool to retrieve a hybrid (aerial + labels) map tile.
Get IsolinesTool to calculate isolines.
Get Label TileTool to retrieve a label overlay tile.
Get Line Overlay TileTool to retrieve a line overlay tile.
Get Map ImageTool to retrieve a static map image.
Get Base Map TileTool to retrieve a base map tile.
Compute Routing MatrixTool to compute a routing distance/time matrix.
Get Meta Info TileTool to retrieve metadata for a specific map tile.
Get POI TileTool to retrieve a point-of-interest overlay tile.
Get Terrain Map TileTool to retrieve a terrain map tile image.
Get Traffic FlowTool to retrieve real-time traffic flow data.
Get Traffic IncidentsTool to fetch real-time traffic incidents within a specified area.
Get Traffic TileTool to retrieve a traffic overlay tile.
Get Waypoint SequenceTool to optimize the visit order of multiple waypoints.
Daily Weather ForecastTool to provide daily weather forecasts (up to 7 days).
Get Weather ObservationTool to retrieve current weather observation.
Hourly Weather ForecastTool to fetch hourly weather forecasts.
Lookup Place DetailsTool to look up detailed information for a place by its HERE ID.
Reverse Geocode CoordinatesTool to convert geographic coordinates into a human-readable address.
Weather AlertsTool to retrieve severe weather alerts for specified locations or routes.
Get Astronomy ForecastTool to fetch astronomical data (sunrise, sunset) for a specific location.

What is the Composio tool router, and how does it fit here?

What is Tool Router?

Composio's Tool Router helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Tool Router

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Tool Router works

The Tool Router follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Prerequisites

Before starting, make sure you have:
  • Node.js 18 or higher
  • A Composio account with an active API key
  • An OpenAI API key
  • Basic familiarity with TypeScript

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key.
  • You need credits or a connected billing setup to use the models.
  • Store the key somewhere safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Go to Settings and copy your API key.
  • This key lets your Mastra agent talk to Composio and reach Here through MCP.

Install dependencies

bash
npm install @composio/core @mastra/core @mastra/mcp @ai-sdk/openai dotenv

Install the required packages.

What's happening:

  • @composio/core is the Composio SDK for creating MCP sessions
  • @mastra/core provides the Agent class
  • @mastra/mcp is Mastra's MCP client
  • @ai-sdk/openai is the model wrapper for OpenAI
  • dotenv loads environment variables from .env

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
COMPOSIO_USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates your requests to Composio
  • COMPOSIO_USER_ID tells Composio which user this session belongs to
  • OPENAI_API_KEY lets the Mastra agent call OpenAI models

Import libraries and validate environment

typescript
import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

const openaiAPIKey = process.env.OPENAI_API_KEY;
const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!openaiAPIKey) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

const composio = new Composio({
  apiKey: composioAPIKey as string,
});
What's happening:
  • dotenv/config auto loads your .env so process.env.* is available
  • openai gives you a Mastra compatible model wrapper
  • Agent is the Mastra agent that will call tools and produce answers
  • MCPClient connects Mastra to your Composio MCP server
  • Composio is used to create a Tool Router session

Create a Tool Router session for Here

typescript
async function main() {
  const session = await composio.create(
    composioUserID as string,
    {
      toolkits: ["here"],
    },
  );

  const composioMCPUrl = session.mcp.url;
  console.log("Here MCP URL:", composioMCPUrl);
What's happening:
  • create spins up a short-lived MCP HTTP endpoint for this user
  • The toolkits array contains "here" for Here access
  • session.mcp.url is the MCP URL that Mastra's MCPClient will connect to

Configure Mastra MCP client and fetch tools

typescript
const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      nasdaq: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

console.log("Fetching MCP tools from Composio...");
const composioTools = await mcpClient.getTools();
console.log("Number of tools:", Object.keys(composioTools).length);
What's happening:
  • MCPClient takes an id for this client and a list of MCP servers
  • The headers property includes the x-api-key for authentication
  • getTools fetches the tool definitions exposed by the Here toolkit

Create the Mastra agent

typescript
const agent = new Agent({
    name: "here-mastra-agent",
    instructions: "You are an AI agent with Here tools via Composio.",
    model: "openai/gpt-5",
  });
What's happening:
  • Agent is the core Mastra agent
  • name is just an identifier for logging and debugging
  • instructions guide the agent to use tools instead of only answering in natural language
  • model uses openai("gpt-5") to configure the underlying LLM

Set up interactive chat interface

typescript
let messages: AiMessageType[] = [];

console.log("Chat started! Type 'exit' or 'quit' to end.\n");

const rl = readline.createInterface({
  input: process.stdin,
  output: process.stdout,
  prompt: "> ",
});

rl.prompt();

rl.on("line", async (userInput: string) => {
  const trimmedInput = userInput.trim();

  if (["exit", "quit", "bye"].includes(trimmedInput.toLowerCase())) {
    console.log("\nGoodbye!");
    rl.close();
    process.exit(0);
  }

  if (!trimmedInput) {
    rl.prompt();
    return;
  }

  messages.push({
    id: crypto.randomUUID(),
    role: "user",
    content: trimmedInput,
  });

  console.log("\nAgent is thinking...\n");

  try {
    const response = await agent.generate(messages, {
      toolsets: {
        here: composioTools,
      },
      maxSteps: 8,
    });

    const { text } = response;

    if (text && text.trim().length > 0) {
      console.log(`Agent: ${text}\n`);
        messages.push({
          id: crypto.randomUUID(),
          role: "assistant",
          content: text,
        });
      }
    } catch (error) {
      console.error("\nError:", error);
    }

    rl.prompt();
  });

  rl.on("close", async () => {
    console.log("\nSession ended.");
    await mcpClient.disconnect();
    process.exit(0);
  });
}

main().catch((err) => {
  console.error("Fatal error:", err);
  process.exit(1);
});
What's happening:
  • messages keeps the full conversation history in Mastra's expected format
  • agent.generate runs the agent with conversation history and Here toolsets
  • maxSteps limits how many tool calls the agent can take in a single run
  • onStepFinish is a hook that prints intermediate steps for debugging

Complete Code

Here's the complete code to get you started with Here and Mastra AI:

typescript
import "dotenv/config";
import { openai } from "@ai-sdk/openai";
import { Agent } from "@mastra/core/agent";
import { MCPClient } from "@mastra/mcp";
import { Composio } from "@composio/core";
import * as readline from "readline";

import type { AiMessageType } from "@mastra/core/agent";

const openaiAPIKey = process.env.OPENAI_API_KEY;
const composioAPIKey = process.env.COMPOSIO_API_KEY;
const composioUserID = process.env.COMPOSIO_USER_ID;

if (!openaiAPIKey) throw new Error("OPENAI_API_KEY is not set");
if (!composioAPIKey) throw new Error("COMPOSIO_API_KEY is not set");
if (!composioUserID) throw new Error("COMPOSIO_USER_ID is not set");

const composio = new Composio({ apiKey: composioAPIKey as string });

async function main() {
  const session = await composio.create(composioUserID as string, {
    toolkits: ["here"],
  });

  const composioMCPUrl = session.mcp.url;

  const mcpClient = new MCPClient({
    id: composioUserID as string,
    servers: {
      here: {
        url: new URL(composioMCPUrl),
        requestInit: {
          headers: session.mcp.headers,
        },
      },
    },
    timeout: 30_000,
  });

  const composioTools = await mcpClient.getTools();

  const agent = new Agent({
    name: "here-mastra-agent",
    instructions: "You are an AI agent with Here tools via Composio.",
    model: "openai/gpt-5",
  });

  let messages: AiMessageType[] = [];

  const rl = readline.createInterface({
    input: process.stdin,
    output: process.stdout,
    prompt: "> ",
  });

  rl.prompt();

  rl.on("line", async (input: string) => {
    const trimmed = input.trim();
    if (["exit", "quit"].includes(trimmed.toLowerCase())) {
      rl.close();
      return;
    }

    messages.push({ id: crypto.randomUUID(), role: "user", content: trimmed });

    const { text } = await agent.generate(messages, {
      toolsets: { here: composioTools },
      maxSteps: 8,
    });

    if (text) {
      console.log(`Agent: ${text}\n`);
      messages.push({ id: crypto.randomUUID(), role: "assistant", content: text });
    }

    rl.prompt();
  });

  rl.on("close", async () => {
    await mcpClient.disconnect();
    process.exit(0);
  });
}

main();

Conclusion

You've built a Mastra AI agent that can interact with Here through Composio's Tool Router. You can extend this further by:
  • Adding other toolkits like Gmail, Slack, or GitHub
  • Building a web-based chat interface around this agent
  • Using multiple MCP endpoints to enable cross-app workflows

How to build Here MCP Agent with another framework

OpenAI Agents SDK

OpenAI Agents SDK

Use Here MCP with OpenAI Agents SDK

Claude Agent SDK

Claude Agent SDK

Use Here MCP with Claude Agent SDK

Google ADK

Google ADK

Use Here MCP with Google ADK

LangChain

LangChain

Use Here MCP with LangChain

Vercel AI SDK

Vercel AI SDK

Use Here MCP with Vercel AI SDK

LlamaIndex

LlamaIndex

Use Here MCP with LlamaIndex

CrewAI

CrewAI

Use Here MCP with CrewAI

FAQ

What are the differences in Tool Router MCP and Here MCP?

With a standalone Here MCP server, the agents and LLMs can only access a fixed set of Here tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Here and many other apps based on the task at hand, all through a single MCP endpoint.

Can I use Tool Router MCP with Mastra AI?

Yes, you can. Mastra AI fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Here tools.

Can I manage the permissions and scopes for Here while using Tool Router?

Yes, absolutely. You can configure which Here scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Here data and credentials are handled as safely as possible.

Used by agents from

Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.

Book a call↗Get started for free