How to Use the Workast MCP in LangChain

Q: How does Workast handle updates in LangChain?

You use the dedicated updatetask tool. This allows your agent to modify existing tasks directly, passing the task ID and the new data payload for immediate change.

Build multi-step Workast workflows with LangChain's agentic chains.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Workast MCP to LangChain

Create your Vinkius account to connect Workast to LangChain and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Workast with LangChain

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Multi-Step Workast Reasoning

Your AI client builds complex, chained operations. If you need to list all projects first (`list_spaces`), the output feeds directly into checking task details for a specific space (`get_task`). This creates an observable sequence of actions. The agent decides which tools run and in what order based on intermediate results. You get full visibility via LangSmith tracing, tracking every input and output.

Managing Workast Data

You can handle the entire lifecycle of project data right through your chain. Need to set up a new workspace? Call `create_space`. Then, when tasks change, you use `update_task` or even wipe them clean with `delete_task`. This makes your MCP Server calls predictable. It's perfect for building internal APIs that manage the full scope of Workast resources: users, teams, and spaces.

Retrieving Account Details

The chain gives you direct access to organizational structure. You can grab a team's roster using `list_users` or pull deep details about specific personnel via `get_user`. This initial data helps the agent decide what subsequent actions are needed. You aren't limited to single calls; you combine these retrievals—say, listing all users and then filtering that list based on roles—all in one continuous flow.

Setup guide

Set up Workast MCP in LangChain

Prerequisites

Python 3.10+ installed
langchain-mcp-adapters + langgraph packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install langchain-mcp-adapters langgraph langchain-openai. The MCP adapters package converts MCP tools into native LangChain BaseTool objects.
2

Connect via HTTP transport
Use MultiServerMCPClient with "transport": "http" pointing to your Vinkius endpoint. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com.
3

Create a ReAct agent
Pass the discovered tools to create_react_agent() from LangGraph. The agent automatically routes Workast tool calls through the MCP protocol.
4

Run with any LLM
Swap ChatOpenAI for ChatAnthropic, ChatGoogleGenerativeAI, or any LangChain-compatible model. The MCP tools work identically across all providers.

agent.py

from langchain_mcp_adapters.client import MultiServerMCPClient
from langgraph.prebuilt import create_react_agent
from langchain_openai import ChatOpenAI

async with MultiServerMCPClient({
    "workast-mcp": {
        "transport": "http",
        "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp",
    }
}) as client:
    tools = client.get_tools()

    agent = create_react_agent(
        ChatOpenAI(model="gpt-4o"),
        tools,
    )
    result = await agent.ainvoke({
        "messages": "List recent Workast transactions"
    })
    print(result["messages"][-1].content)

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Workast. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Workast now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Workast MCP in LangChain

You initialize the MCP Server tools and pass them to your agent constructor. The agent then decides if it needs to call `get_space` or `list_tasks` based on the prompt. You just build the logic; the client handles the execution.

Yes, while stateless by default, you can manage persistent context using the client's session function. This lets your multi-step workflow remember previous results or user inputs across multiple tool calls.

This MCP Server touches core organizational structures, specifically Space details (`get_space`), User records (`get_user`), and Task information. Your agent can interact with all these resource types.

Absolutely. The unique power is chaining. You aren't limited to single calls; you can run `list_spaces`, pass the resulting IDs, and then call `get_team_info` sequentially within one agentic pipeline.

You use the dedicated `update_task` tool. This allows your agent to modify existing tasks directly, passing the task ID and the new data payload for immediate change.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript