Introducing Gram ๐

Gram is the complete MCP cloud. Create and curate high quality agentic tools. Deploy and host your MCP servers in minutes. It is secure, fully OAuth-enabled, and ready to scale for production use.
The Model Context Protocol (MCP)ย
import { Gram } from "@gram-ai/functions";
import * as z from "zod/mini";
const gram = new Gram().tool({
name: "greet",
description: "Greet someone special",
inputSchema: { name: z.string() },
async execute(ctx, input) {
return ctx.text(`Hello, ${input.name}!`);
},
});
export default gram;Use Gram to build out MCP servers for your product, power chat experiences in your product, or surface the right data to AI agents to automate workflows.
Why MCP?
LLMs and agents need access to context-specific data to perform useful tasks. This data is often found behind an authenticated service, in a database, or in stored content. MCP is the standard protocol for defining tools that AI agents can use to connect to the external systems where this data is located.
Since it was announced by Anthropic in November 2024, MCP has seen an unprecedented rate of adoption, quickly becoming the de facto standard. Companies like Microsoft, Google, OpenAI, and Cloudflare (among many others) have embraced it and offer MCP servers as a new way to interact with their products and APIs.
But creating, deploying, hosting, and managing the lifecycle of MCP servers remains confusing and challenging. Although MCP follows a familiar client-server model, it creates confusion about who should build, own, manage, and maintain the server. With APIs, itโs always been clear. The producer (like Stripe) hosts the API, and the consumer (for example, an online shop) uses that API. With MCP, hosting models vary: Developers often โhostโ MCP servers on their own machines, or companies host them internally for team-wide access to internal APIs or third-party integrations.
We think that companies will naturally gravitate toward hosting and managing their own MCP servers, and we built Gram to make that easy.
Why Gram?
Gram aims to give you a comprehensive experience and unlock the value of MCP without the need to build complete servers.
To realise this vision, Gram is built using the following principles:
๐น Simplicity: Easy to use, easy to understand, easy to maintain
๐น Performant and managed: Offers fast and serverless infrastructure that you can rely on
๐น Secure: Provides built-in security and best practices for working with agentic tools
๐น Works with your stack: Helps you leverage existing APIs to bootstrap tools
Gram is made with love โค๏ธ and โ๏ธ by the team at Speakeasy.
LLM-friendly docs
This documentation site is also available in llms.txtย
The llms.txt references two ways to access the LLM-friendly documentation:
llms-small.txtis the abridged developer documentation for the site.llms-full.txtcontains the entire documentation. Note that this may exceed the context window of your LLM.
You can also copy any page into markdown or open it into popular LLM chat clients (like ChatGPT or Claude) using the dropdown at the top of the right-hand navigation bar.
Further reading
- Building tools in TypeScript using Gram Functions
- Getting started with Gram using an API spec
- Bring an existing MCP server to Gram
- For resources on MCP, see our MCP hub
- Adding OAuth to your MCP server
- CLI reference
Last updated on