@mastra/mcp-docs-server 0.13.39 → 1.0.0-beta.0

package/.docs/raw/reference/tools/mcp-server.mdx

@@ -24,6 +24,7 @@ import { z } from "zod";
 import { dataProcessingWorkflow } from "../workflows/dataProcessingWorkflow";
 
 const myAgent = new Agent({
+  id: "my-example-agent",
   name: "MyExampleAgent",
   description: "A generalist to help with basic questions."
   instructions: "You are a helpful assistant.",
@@ -34,10 +35,11 @@ const weatherTool = createTool({
   id: "getWeather",
   description: "Gets the current weather for a location.",
   inputSchema: z.object({ location: z.string() }),
-  execute: async ({ context }) => `Weather in ${context.location} is sunny.`,
+  execute: async (inputData) => `Weather in ${inputData.location} is sunny.`,
 });
 
 const server = new MCPServer({
+  id: "my-custom-server",
   name: "My Custom Server",
   version: "1.0.0",
   tools: { weatherTool },
@@ -54,6 +56,13 @@ The constructor accepts an `MCPServerConfig` object with the following propertie
 
 <PropertiesTable
   content={[
+    {
+      name: "id",
+      type: "string",
+      isOptional: false,
+      description:
+        "Unique identifier for the server. This ID is preserved when the server is registered with Mastra and can be used to retrieve the server via getMCPServerById().",
+    },
     {
       name: "name",
       type: "string",
@@ -86,14 +95,7 @@ The constructor accepts an `MCPServerConfig` object with the following propertie
       type: "Record<string, Workflow>",
       isOptional: true,
       description:
-        "An object where keys are workflow identifiers and values are Mastra Workflow instances. Each workflow is converted into a tool named `run_<workflowKey>`. The workflow's `inputSchema` becomes the tool's input schema. The workflow **must** have a non-empty `description` string property, which is used for the tool's description. If a workflow's description is missing or empty, an error will be thrown. The tool executes the workflow by calling `workflow.createRunAsync()` followed by `run.start({ inputData: <tool_input> })`. If a tool name derived from an agent or workflow (e.g., `ask_myAgent` or `run_myWorkflow`) collides with an explicitly defined tool name or another derived name, the explicitly defined tool takes precedence, and a warning is logged. Agents/workflows leading to subsequent collisions are skipped.",
-    },
-    {
-      name: "id",
-      type: "string",
-      isOptional: true,
-      description:
-        "Optional unique identifier for the server. If not provided, a UUID will be generated. This ID is considered final and cannot be changed by Mastra if provided.",
+        "An object where keys are workflow identifiers and values are Mastra Workflow instances. Each workflow is converted into a tool named `run_<workflowKey>`. The workflow's `inputSchema` becomes the tool's input schema. The workflow **must** have a non-empty `description` string property, which is used for the tool's description. If a workflow's description is missing or empty, an error will be thrown. The tool executes the workflow by calling `workflow.createRun()` followed by `run.start({ inputData: <tool_input> })`. If a tool name derived from an agent or workflow (e.g., `ask_myAgent` or `run_myWorkflow`) collides with an explicitly defined tool name or another derived name, the explicitly defined tool takes precedence, and a warning is logged. Agents/workflows leading to subsequent collisions are skipped.",
     },
     {
       name: "description",
@@ -200,7 +202,10 @@ Here's how you would start the server using stdio:
 
 ```typescript
 const server = new MCPServer({
-  // example configuration above
+  id: "my-server",
+  name: "My Server",
+  version: "1.0.0",
+  tools: { /* ... */ },
 });
 await server.startStdio();
 ```
@@ -387,7 +392,7 @@ const httpServer = http.createServer(async (req, res) => {
     req,
     res,
     options: {
-      sessionIdGenerator: undefined,
+      sessionIdGenerator: () => randomUUID(),
     },
   });
 });
@@ -397,6 +402,75 @@ httpServer.listen(PORT, () => {
 });
 ```
 
+For **serverless environments** (Supabase Edge Functions, Cloudflare Workers, Vercel Edge, etc.), use `serverless: true` to enable stateless operation:
+
+```typescript
+// Supabase Edge Function example
+import { serve } from "https://deno.land/std@0.168.0/http/server.ts";
+import { MCPServer } from "@mastra/mcp";
+// Note: You will need to convert req/res format from Deno to Node
+import { toReqRes, toFetchResponse } from "fetch-to-node";
+
+const server = new MCPServer({
+  id: "my-serverless-mcp",
+  name: "My Serverless MCP",
+  version: "1.0.0",
+  tools: { /* your tools */ },
+});
+
+serve(async (req) => {
+  const url = new URL(req.url);
+  
+  if (url.pathname === "/mcp") {
+    // Convert Deno Request to Node.js-compatible format
+    const { req: nodeReq, res: nodeRes } = toReqRes(req);
+    
+    await server.startHTTP({
+      url,
+      httpPath: "/mcp",
+      req: nodeReq,
+      res: nodeRes,
+      options: {
+        serverless: true, // ← Enable stateless mode for serverless
+      },
+    });
+    
+    return toFetchResponse(nodeRes);
+  }
+  
+  return new Response("Not found", { status: 404 });
+});
+```
+
+:::info
+
+**When to use `serverless: true`**
+
+Use `serverless: true` when deploying to environments where each request runs in a fresh, stateless execution context:
+- Supabase Edge Functions
+- Cloudflare Workers
+- Vercel Edge Functions
+- Netlify Edge Functions
+- AWS Lambda
+- Deno Deploy
+
+Use the default session-based mode (without `serverless: true`) for:
+- Long-lived Node.js servers
+- Docker containers
+- Traditional hosting (VPS, dedicated servers)
+
+The serverless mode disables session management and creates fresh server instances per request, which is necessary for stateless environments where memory doesn't persist between invocations.
+
+**Note:** The following MCP features require session state or persistent connections and will **not work** in serverless mode:
+- **Elicitation** - Interactive user input requests during tool execution require session management to route responses back to the correct client
+- **Resource subscriptions** - `resources/subscribe` and `resources/unsubscribe` need persistent connections to maintain subscription state
+- **Resource update notifications** - `resources.notifyUpdated()` requires active subscriptions and persistent connections to notify clients
+- **Prompt list change notifications** - `prompts.notifyListChanged()` requires persistent connections to push updates to clients
+
+These features work normally in long-lived server environments (Node.js servers, Docker containers, etc.).
+
+:::
+
 Here are the details for the values needed by the `startHTTP` method:
 
 <PropertiesTable
@@ -437,6 +511,13 @@ The `StreamableHTTPServerTransportOptions` object allows you to customize the be
 
 <PropertiesTable
   content={[
+    {
+      name: "serverless",
+      type: "boolean",
+      description:
+        "If `true`, runs in stateless mode without session management. Each request is handled independently with a fresh server instance. Essential for serverless environments (Cloudflare Workers, Supabase Edge Functions, Vercel Edge, etc.) where sessions cannot persist between invocations. Defaults to `false`.",
+      optional: true,
+    },
     {
       name: "sessionIdGenerator",
       type: "(() => string) | undefined",
@@ -668,6 +749,7 @@ const myResourceHandlers: MCPServerResources = {
 };
 
 const serverWithResources = new MCPServer({
+  id: "resourceful-server",
   name: "Resourceful Server",
   version: "1.0.0",
   tools: {
@@ -800,6 +882,7 @@ const myPromptHandlers: MCPServerPrompts = {
 };
 
 const serverWithPrompts = new MCPServer({
+  id: "promptful-server",
   name: "Promptful Server",
   version: "1.0.0",
   tools: {
@@ -835,7 +918,7 @@ await serverWithPrompts.prompts.notifyListChanged();
 
 ## Examples
 
-For practical examples of setting up and deploying an MCPServer, see the [Deploying an MCPServer Example](/examples/agents/deploying-mcp-server).
+For practical examples of setting up and deploying an MCPServer, see the [Deploying an MCPServer Example](/examples/v1/agents/deploying-mcp-server).
 
 The example at the beginning of this page also demonstrates how to instantiate `MCPServer` with both tools and agents.
 
@@ -845,24 +928,24 @@ The example at the beginning of this page also demonstrates how to instantiate `
 
 Elicitation is a feature in the Model Context Protocol (MCP) that allows servers to request structured information from users. This enables interactive workflows where servers can collect additional data dynamically.
 
-The `MCPServer` class automatically includes elicitation capabilities. Tools receive an `options` parameter in their `execute` function that includes an `elicitation.sendRequest()` method for requesting user input.
+The `MCPServer` class automatically includes elicitation capabilities. Tools receive a `context.mcp` object in their `execute` function that includes an `elicitation.sendRequest()` method for requesting user input.
 
 ### Tool Execution Signature
 
-When tools are executed within an MCP server context, they receive an additional `options` parameter:
+When tools are executed within an MCP server context, they receive MCP-specific capabilities via the `context.mcp` object:
 
 ```typescript
-execute: async ({ context }, options) => {
-  // context contains the tool's input parameters
-  // options contains server capabilities like elicitation and authentication info
+execute: async (inputData, context) => {
+  // input contains the tool's inputData parameters
+  // context.mcp contains server capabilities like elicitation and authentication info
 
   // Access authentication information (when available)
-  if (options.extra?.authInfo) {
-    console.log("Authenticated request from:", options.extra.authInfo.clientId);
+  if (context.mcp?.extra?.authInfo) {
+    console.log("Authenticated request from:", context.mcp.extra.authInfo.clientId);
   }
 
   // Use elicitation capabilities
-  const result = await options.elicitation.sendRequest({
+  const result = await context.mcp.elicitation.sendRequest({
     message: "Please provide information",
     requestedSchema: {
       /* schema */
@@ -875,9 +958,9 @@ execute: async ({ context }, options) => {
 
 ### How Elicitation Works
 
-A common use case is during tool execution. When a tool needs user input, it can use the elicitation functionality provided through the tool's execution options:
+A common use case is during tool execution. When a tool needs user input, it can use the elicitation functionality provided through the context parameter:
 
-1. The tool calls `options.elicitation.sendRequest()` with a message and schema
+1. The tool calls `context.mcp.elicitation.sendRequest()` with a message and schema
 2. The request is sent to the connected MCP client
 3. The client presents the request to the user (via UI, command line, etc.)
 4. The user provides input, declines, or cancels the request
@@ -894,6 +977,7 @@ import { createTool } from "@mastra/core/tools";
 import { z } from "zod";
 
 const server = new MCPServer({
+  id: "interactive-server",
   name: "Interactive Server",
   version: "1.0.0",
   tools: {
@@ -906,15 +990,15 @@ const server = new MCPServer({
           .optional()
           .describe("Reason for collecting contact info"),
       }),
-      execute: async ({ context }, options) => {
-        const { reason } = context;
+      execute: async (inputData, context) => {
+        const { reason } = inputData;
 
         // Log session info if available
-        console.log("Request from session:", options.extra?.sessionId);
+        console.log("Request from session:", context.mcp?.extra?.sessionId);
 
         try {
           // Request user input via elicitation
-          const result = await options.elicitation.sendRequest({
+          const result = await context.mcp.elicitation.sendRequest({
             message: reason
               ? `Please provide your contact information. ${reason}`
               : "Please provide your contact information",
@@ -1022,16 +1106,16 @@ The elicitation functionality is available through the `options` parameter in to
 
 ```typescript
 // Within a tool's execute function
-execute: async ({ context }, options) => {
+execute: async (inputData, context) => {
   // Use elicitation for user input
-  const result = await options.elicitation.sendRequest({
+  const result = await context.mcp.elicitation.sendRequest({
     message: string,           // Message to display to user
     requestedSchema: object    // JSON schema defining expected response structure
   }): Promise<ElicitResult>
 
   // Access authentication info if needed
-  if (options.extra?.authInfo) {
-    // Use options.extra.authInfo.token, etc.
+  if (context.mcp?.extra?.authInfo) {
+    // Use context.mcp.extra.authInfo.token, etc.
   }
 }
 ```
@@ -1049,18 +1133,18 @@ type ElicitResult = {
 
 ## Authentication Context
 
-Tools can access request metadata via `options.extra` when using HTTP-based transports:
+Tools can access request metadata via `context.mcp.extra` when using HTTP-based transports:
 
 ```typescript
-execute: async ({ context }, options) => {
-  if (!options.extra?.authInfo?.token) {
+execute: async (inputData, context) => {
+  if (!context.mcp?.extra?.authInfo?.token) {
     return "Authentication required";
   }
 
   // Use the auth token
   const response = await fetch("/api/data", {
-    headers: { Authorization: `Bearer ${options.extra.authInfo.token}` },
-    signal: options.extra.signal,
+    headers: { Authorization: `Bearer ${context.mcp.extra.authInfo.token}` },
+    signal: context.mcp.extra.signal,
   });
 
   return response.json();

package/.docs/raw/reference/tools/vector-query-tool.mdx

@@ -28,7 +28,7 @@ const queryTool = createVectorQueryTool({
 :::note
 
 **Parameter Requirements:** Most fields can be set at creation as defaults.
-Some fields can be overridden at runtime via the runtime context or input. If
+Some fields can be overridden at runtime via the request context or input. If
 a required field is missing from both creation and runtime, an error will be
 thrown. Note that `model`, `id`, and `description` can only be set at creation
 time.
@@ -76,7 +76,7 @@ time.
       name: "enableFilter",
       type: "boolean",
       description:
-        "Enable filtering of results based on metadata. (Set at creation only, but will be automatically enabled if a filter is provided in the runtime context.)",
+        "Enable filtering of results based on metadata. (Set at creation only, but will be automatically enabled if a filter is provided in the request context.)",
       isOptional: true,
       defaultValue: "false",
     },
@@ -326,7 +326,7 @@ This agent-driven approach:
 
 For detailed filter syntax and store-specific capabilities, see the [Metadata Filters](../rag/metadata-filters) documentation.
 
-For an example of how agent-driven filtering works, see the [Agent-Driven Metadata Filtering](/examples/rag/usage/filter-rag) example.
+For an example of how agent-driven filtering works, see the [Agent-Driven Metadata Filtering](/examples/v1/rag/usage/filter-rag) example.
 
 ## Example with Reranking
 
@@ -496,7 +496,7 @@ The `databaseConfig` parameter allows you to leverage unique features and optimi
 You can override database configurations at runtime to adapt to different scenarios:
 
 ```typescript
-import { RuntimeContext } from "@mastra/core/runtime-context";
+import { RequestContext } from "@mastra/core/request-context";
 
 const queryTool = createVectorQueryTool({
   vectorStoreName: "pinecone",
@@ -510,15 +510,15 @@ const queryTool = createVectorQueryTool({
 });
 
 // Override at runtime
-const runtimeContext = new RuntimeContext();
-runtimeContext.set("databaseConfig", {
+const requestContext = new RequestContext();
+requestContext.set("databaseConfig", {
   pinecone: {
     namespace: "production", // Switch to production namespace
   },
 });
 
 const response = await agent.generate("Find information about deployment", {
-  runtimeContext,
+  requestContext,
 });
 ```
 
@@ -528,7 +528,7 @@ This approach allows you to:
 - Adjust performance parameters based on load
 - Apply different filtering strategies per request
 
-## Example: Using Runtime Context
+## Example: Using Request Context
 
 ```typescript
 const queryTool = createVectorQueryTool({
@@ -538,37 +538,37 @@ const queryTool = createVectorQueryTool({
 });
 ```
 
-When using runtime context, provide required parameters at execution time via the runtime context:
+When using request context, provide required parameters at execution time via the request context:
 
 ```typescript
-const runtimeContext = new RuntimeContext<{
+const requestContext = new RequestContext<{
   vectorStoreName: string;
   indexName: string;
   topK: number;
   filter: VectorFilter;
   databaseConfig: DatabaseConfig;
 }>();
-runtimeContext.set("vectorStoreName", "my-store");
-runtimeContext.set("indexName", "my-index");
-runtimeContext.set("topK", 5);
-runtimeContext.set("filter", { category: "docs" });
-runtimeContext.set("databaseConfig", {
+requestContext.set("vectorStoreName", "my-store");
+requestContext.set("indexName", "my-index");
+requestContext.set("topK", 5);
+requestContext.set("filter", { category: "docs" });
+requestContext.set("databaseConfig", {
   pinecone: { namespace: "runtime-namespace" },
 });
-runtimeContext.set("model", openai.embedding("text-embedding-3-small"));
+requestContext.set("model", openai.embedding("text-embedding-3-small"));
 
 const response = await agent.generate(
   "Find documentation from the knowledge base.",
   {
-    runtimeContext,
+    requestContext,
   },
 );
 ```
 
-For more information on runtime context, please see:
+For more information on request context, please see:
 
-- [Agent Runtime Context](/docs/server-db/runtime-context)
-- [Tool Runtime Context](/docs/tools-mcp/overview#using-runtimecontext)
+- [Agent Request Context](/docs/v1/server-db/request-context)
+- [Tool Request Context](/docs/v1/tools-mcp/overview#using-requestcontext)
 
 ## Usage Without a Mastra Server
 
@@ -576,11 +576,12 @@ The tool can be used by itself to retrieve documents matching a query:
 
 ```typescript copy showLineNumbers title="src/index.ts"
 import { openai } from "@ai-sdk/openai";
-import { RuntimeContext } from "@mastra/core/runtime-context";
+import { RequestContext } from "@mastra/core/request-context";
 import { createVectorQueryTool } from "@mastra/rag";
 import { PgVector } from "@mastra/pg";
 
 const pgVector = new PgVector({
+  id: 'pg-vector',
   connectionString: process.env.POSTGRES_CONNECTION_STRING!,
 });
 
@@ -591,11 +592,11 @@ const vectorQueryTool = createVectorQueryTool({
   model: openai.embedding("text-embedding-3-small"),
 });
 
-const runtimeContext = new RuntimeContext();
-const queryResult = await vectorQueryTool.execute({
-  context: { queryText: "foo", topK: 1 },
-  runtimeContext,
-});
+const requestContext = new RequestContext();
+const queryResult = await vectorQueryTool.execute(
+  { queryText: "foo", topK: 1 },
+  { requestContext }
+);
 
 console.log(queryResult.sources);
 ```

package/.docs/raw/reference/vectors/libsql.mdx

@@ -21,6 +21,7 @@ import { LibSQLVector } from "@mastra/libsql";
 
 // Create a new vector store instance
 const store = new LibSQLVector({
+  id: 'libsql-vector',
   connectionUrl: process.env.DATABASE_URL,
   // Optional: for Turso cloud databases
   authToken: process.env.DATABASE_AUTH_TOKEN,

package/.docs/raw/reference/vectors/pg.mdx

@@ -90,6 +90,7 @@ It provides robust vector similarity search capabilities within your existing Po
 import { PgVector } from "@mastra/pg";
 
 const vectorStore = new PgVector({
+  id: 'pg-vector',
   connectionString: "postgresql://user:password@localhost:5432/mydb",
 });
 ```
@@ -98,6 +99,7 @@ const vectorStore = new PgVector({
 
 ```ts
 const vectorStore = new PgVector({
+  id: 'pg-vector',
   host: "localhost",
   port: 5432,
   database: "mydb",
@@ -110,6 +112,7 @@ const vectorStore = new PgVector({
 
 ```ts
 const vectorStore = new PgVector({
+  id: 'pg-vector',
   connectionString: "postgresql://user:password@localhost:5432/mydb",
   schemaName: "custom_schema",
   max: 30,

package/.docs/raw/reference/vectors/upstash.mdx

@@ -242,6 +242,7 @@ Upstash Vector supports hybrid search that combines semantic search (dense vecto
 import { UpstashVector } from "@mastra/upstash";
 
 const vectorStore = new UpstashVector({
+  id: 'upstash-vector',
   url: process.env.UPSTASH_VECTOR_URL,
   token: process.env.UPSTASH_VECTOR_TOKEN,
 });

package/.docs/raw/reference/voice/google-gemini-live.mdx

@@ -218,7 +218,7 @@ Establishes a connection to the Gemini Live API. Must be called before using spe
 <PropertiesTable
   content={[
     {
-      name: "runtimeContext",
+      name: "requestContext",
       type: "object",
       description: "Optional request context for the connection.",
       isOptional: true,

package/.docs/raw/reference/voice/voice.addTools.mdx

@@ -24,14 +24,14 @@ const weatherTool = createTool({
   outputSchema: z.object({
     message: z.string(),
   }),
-  execute: async ({ context }) => {
+  execute: async (inputData) => {
     // Fetch weather data from an API
     const response = await fetch(
-      `https://api.weather.com?location=${encodeURIComponent(context.location)}`,
+      `https://api.weather.com?location=${encodeURIComponent(inputData.location)}`,
     );
     const data = await response.json();
     return {
-      message: `The current temperature in ${context.location} is ${data.temperature}°F with ${data.conditions}.`,
+      message: `The current temperature in ${inputData.location} is ${data.temperature}°F with ${data.conditions}.`,
     };
   },
 });

package/.docs/raw/reference/workflows/run-methods/cancel.mdx

@@ -10,7 +10,7 @@ The `.cancel()` method cancels a workflow run, stopping execution and cleaning u
 ## Usage example
 
 ```typescript showLineNumbers copy
-const run = await workflow.createRunAsync();
+const run = await workflow.createRun();
 
 await run.cancel();
 ```
@@ -44,7 +44,7 @@ await run.cancel();
 ## Extended usage example
 
 ```typescript showLineNumbers copy
-const run = await workflow.createRunAsync();
+const run = await workflow.createRun();
 
 try {
   const result = await run.start({ inputData: { value: "initial data" } });
@@ -55,5 +55,5 @@ try {
 
 ## Related
 
-- [Workflows overview](/docs/workflows/overview#running-workflows)
-- [Workflow.createRunAsync()](../workflow-methods/create-run)
+- [Workflows overview](/docs/v1/workflows/overview#running-workflows)
+- [Workflow.createRun()](../workflow-methods/create-run)

package/.docs/raw/reference/workflows/run-methods/resume.mdx

@@ -10,7 +10,7 @@ The `.resume()` method resumes a suspended workflow run with new data, allowing
 ## Usage example
 
 ```typescript showLineNumbers copy
-const run = await workflow.createRunAsync();
+const run = await workflow.createRun();
 
 const result = await run.start({ inputData: { value: "initial data" } });
 
@@ -39,9 +39,9 @@ if (result.status === "suspended") {
       isOptional: true,
     },
     {
-      name: "runtimeContext",
-      type: "RuntimeContext",
-      description: "Runtime context data to use when resuming",
+      name: "requestContext",
+      type: "RequestContext",
+      description: "Request Context data to use when resuming",
       isOptional: true,
     },
     {
@@ -55,16 +55,16 @@ if (result.status === "suspended") {
       type: "TracingContext",
       isOptional: true,
       description:
-        "AI tracing context for creating child spans and adding metadata. Automatically injected when using Mastra's tracing system.",
+        "Tracing context for creating child spans and adding metadata. Automatically injected when using Mastra's tracing system.",
       properties: [
         {
           parameters: [
             {
               name: "currentSpan",
-              type: "AISpan",
+              type: "Span",
               isOptional: true,
               description:
-                "Current AI span for creating child spans and adding metadata. Use this to create custom child spans or update span attributes during execution.",
+                "Current span for creating child spans and adding metadata. Use this to create custom child spans or update span attributes during execution.",
             },
           ],
         },
@@ -74,7 +74,7 @@ if (result.status === "suspended") {
       name: "tracingOptions",
       type: "TracingOptions",
       isOptional: true,
-      description: "Options for AI tracing configuration.",
+      description: "Options for Tracing configuration.",
       properties: [
         {
           parameters: [
@@ -93,7 +93,7 @@ if (result.status === "suspended") {
       name: "outputOptions",
       type: "OutputOptions",
       isOptional: true,
-      description: "Options for AI tracing configuration.",
+      description: "Options for output configuration.",
       properties: [
         {
           parameters: [
@@ -126,7 +126,7 @@ if (result.status === "suspended") {
       type: "string",
       isOptional: true,
       description:
-        "The trace ID associated with this execution when AI tracing is enabled. Use this to correlate logs and debug execution flow.",
+        "The trace ID associated with this execution when Tracing is enabled. Use this to correlate logs and debug execution flow.",
     },
   ]}
 />
@@ -146,7 +146,7 @@ if (result.status === "suspended") {
 
 ## Related
 
-- [Workflows overview](/docs/workflows/overview#running-workflows)
-- [Workflow.createRunAsync()](../workflow-methods/create-run)
-- [Suspend and resume](/docs/workflows/suspend-and-resume)
-- [Human in the loop example](/examples/workflows_legacy/human-in-the-loop)
+- [Workflows overview](/docs/v1/workflows/overview#running-workflows)
+- [Workflow.createRun()](../workflow-methods/create-run)
+- [Suspend and resume](/docs/v1/workflows/suspend-and-resume)
+- [Human in the loop](/docs/v1/workflows/human-in-the-loop)