GitHub Copilot Archives - Creospan

Why Model Context Protocol Matters: Building Real-World Workflows

Donna Mathew — Thu, 22 Jan 2026 17:59:42 +0000

When large language models (LLMs) first became accessible, most of our interactions with them were bound within a single prompt-response cycle. You asked, they answered. But as developers began embedding AI into real systems (IDE copilot etc.), it became clear that prompts alone couldn’t sustain meaningful workflows. AI needed context, memory, and the ability to act, not just chat. That’s where the Model Context Protocol (MCP) enters the picture (to solve the context and ability needs).

At its core, MCP is an open standard that lets AI models connect to external systems in a structured, context-aware way. Think of it as the connective tissue between an AI and the tools it depends on; databases, project trackers, and code environments. Rather than reinventing integrations for each tool, MCP solves the integration bottleneck for agentic systems and enables real-time, context-aware automation.

Why Not Just Call APIs Directly?

Why not let the model talk directly to the tool’s API?

The short answer is control and security.

MCP defines a client-server pattern that allows AI systems to interact with real-world applications through a common interface. This allows models to securely call external tools, fetch structured data, and perform actions without the LLM needing to know every detail about the API behind it. It standardizes how models “see” tools, what they can access, and how they act to keep everything modular, secure, and interoperable.

How it Works

In a typical MCP architecture, an LLM communicates through an MCP client, which routes requests to one or more MCP servers. The client handles translation between the model’s natural language intent and the technical request schema, while the server executes the actual tool actions like storing data, fetching content, or performing updates. Some IDE environments, such as Cursor, already act as an MCP client under the hood, enabling seamless communication with compatible servers. This design separates the language model from the tool’s raw APIs.

Our Workflow: IDE Centered Intelligence with MCP

At Creospan, we deliberately designed our MCP based workflow around a simple but important belief: meaningful engineering decisions require code-level context. While large language models can reason over user stories and tickets in isolation, real prioritization, dependency analysis, and implementation planning only become reliable when the model understands the actual code, it is going to change. This is precisely the gap MCP helps us bridge.

This is why our workflow places the IDE, not the task tracker or project planning tool, at the center.

At Creopsan, Linear serves as our project management tool. Linear is a high-performance project management tool designed to streamline software development workflows through a minimalist interface. It holds user stories, priorities, and labels. However, instead of treating Linear as the place where decisions are made, we treat it as a structured input source. Through an MCP connection, stories flow from Linear directly into the coding environment, where they can be evaluated with full visibility into the codebase using AI Assisted IDE’s context engine.

Once inside the AI Assisted IDE (Cursor, GitHub Copilot, Augment Code, etc.), the LLM operates with two critical forms of context. The first is project management context, fetched from Linear via MCP. The second is implementation context, derived from the code repository itself using the IDE’S context engine which maintains a live understanding of the stack across repositories, services, and code history.

This combination enables a class of reasoning that is difficult to achieve elsewhere. As stories are loaded into the IDE, the LLM can reason across them to surface overlaps, shared implementation paths, and implicit relationships. Similar stories can be grouped not just based on description but based on the parts of the codebase they affect. Common work emerges naturally when multiple tickets map to the same components or abstractions. Ordering concerns surface by inspecting dependencies in code rather than relying solely on ticket-level links.

Importantly, this reasoning is not fully automated or opaque. The LLM proposes insights and prioritization suggestions, but developers remain in the loop. Engineers validate, adjust, or override decisions with a clear understanding of why a particular ordering or grouping was suggested. MCP makes this possible by ensuring that product intent from Linear and technical reality from the codebase using context engine are available together inside the IDE.

Once decisions are validated, the workflow completes its loop. Updates, refinements, and execution outcomes are pushed back into Linear via MCP, keeping the product view synchronized without forcing developers to leave their editor. Developers can then pick up a story, begin implementation, and update its status directly from the IDE. Every change, discussion, and update stay synchronized, giving stakeholders a live view of progress while preserving developer flow.

Notion as the Learning Layer

If Linear captures what we plan to build, Notion captures how we build it. Notion is an all-in-one workspace that blends note-taking, document collaboration, and database management into a single, highly customizable platform. Through a separate MCP server, we log meaningful AI interactions from the IDE into Notion. This includes prompts that led to better architectural decisions, reasoning traces behind prioritization choices, and patterns that repeat across projects. Over time, these logs have evolved into a knowledge dataset, a reflection of how our team collaborates with AI. By analyzing them, we uncover which prompts drive faster development or cleaner code, and which patterns repeat across projects. The most effective ones become shared templates, enabling the entire team to improve collectively rather than individually.

The result is a connected system where planning, implementation, and learning reinforce each other through shared context. MCP’s value lies not in tool integration itself, but in enabling intelligence to operate within the IDE, where code and product intent converges.

At Creospan, we see this as a key step forward for SDLC productivity, where small efficiencies compound across teams and projects. In the end, our implementation shows how AI systems can evolve from reactive to proactive. Tools like Notion and Linear are not just endpoints; they are contexts. With MCP, we give AI the means to understand, navigate, and contribute to those contexts intelligently.

Conclusion

As AI continues to reshape the landscape of software development, MCP stands out as a transformative standard for building agentic, context-aware workflows. By bridging product intent and technical reality within the IDE, MCP empowers both AI and human collaborators to make informed, reliable decisions driving productivity and innovation across teams. The recent evolution of MCP, with enhanced security, structured tool output, and seamless IDE integrations, positions it not just as a technical solution but as a foundation for the next generation of intelligent engineering systems.

Article Written By Dhairya Bhuta

The post Why Model Context Protocol Matters: Building Real-World Workflows appeared first on Creospan.

What is Vibe Coding?

Donna Mathew — Fri, 14 Mar 2025 14:06:11 +0000

What is Vibe Coding?

Vibe coding isn’t an official term. It’s more of a coding mindset. Vibe coding is a programming approach that leverages AI tools to create code based on natural language descriptions of desired functionality. In this method of developing code, we rely heavily on autocomplete, AI coding assistants like GitHub Copilot or ChatGPT or various AI Coding Editing tools, and use existing code examples, all while making decisions based on intuition rather than structured instruction.

How it Works:

Instead of manually coding line by line, developers provide instructions to AI-powered coding platforms, which generate code blocks based on prompt inputs.

Examples of Vibe AI Coding Tools:

Platforms like Cursor, Bolt, and Claude exemplify vibe coding technology, assisting developers in the code-generation process.

I know some of you might already be using Copilot with VS Code which in itself is vibe coding, But you want to elevate your ability “You want a fully-featured IDE with AI capabilities built-in” or “You need flexibility in choosing AI models (GPT-4, Claude, etc.)” or “You prefer using your own API keys to control costs” you can try using any of the Vibe AI Coding tools, and you can start with one : https://www.cursor.com/

Role Transformation for Programmers:

Vibe coding alters the programmer’s role, emphasizing tasks like guiding, testing, and refining AI-generated source code rather than writing it manually.

A Creative Shift in the Programming Mindset

Vibe coding represents a larger cultural shift in how people approach software creation. It lowers the psychological barrier for beginners, prioritizes creativity over precision, and embraces of experimentation.

Vibe coding accelerates the AI transformation. When anyone can generate functional code through conversation/Prompt Engineering, the specialization that once protected technical roles evaporates. The implications ripple through organizations and everyone has an elevated role to play:

For Product managers would not hide behind documents/wireframes — they would be generating working prototypes.
For Designers can’t just hand off mockups — they’ll will have a role to implement their designs.
For Marketers can’t request custom tools — they’ll be building their own analytics dashboards
For Executives can’t survive technical ignorance — they’ll need to understand the systems they oversee.

The Build Vs Run/Maintenance Model

Vibe coding excels at build but struggles with Maintenance/Run. This creates a fundamental split:

Creation/Building New: Easy, accessible, new functionality.
Maintenance/Run: Complex, requiring deep business expertise, increasingly valuable.

Smart Innovative organizations will develop dual skillsets — rapid vibe coding for prototyping and proof-of-concepts, alongside rigorous engineering practices for enterprise grade systems.

Programming Evolution:
Vibe coding reflects programming’s evolution, with developers potentially transitioning into roles as “AI architects.”

Benefits:

This approach can speed up software development, give Iron man suite to existing developers, empower non-developers to create applications, and foster creativity without requiring deep coding expertise.

Concerns:

Developers must still understand underlying syntax and code, ensure quality, and address security issues, as these remain critical in AI-assisted coding.

Finding the Right Balance: Augmentation, Not Replacement

I would not suggest abandoning AI-assisted coding ship — that would be like rejecting power tools in favor of manual screwdriver. But we need to approach this revolution thoughtfully, preserving the craftsmanship while embracing innovation.

Article Written by Krishnam Raju Bhupathiraju.

The post What is Vibe Coding? appeared first on Creospan.

AI Agents – The Future of Workforce

Donna Mathew — Mon, 19 Aug 2024 22:06:58 +0000

I am sure you can relate to preparing sheets of information about the number of employees in your team, and how the budget is allocated through projects/tasks in your current or previous roles. It is not far you will have to add another dimension to it, how many of them are human and how many are non-human (AI Agents).

AI agents leverage large language models like GPT etc. to understand goals, generate tasks, and go on completing them. We can deploy them to automate work and outsource complex cognitive tasks, creating a team of robotic coworkers.

This field is evolving faster than ever, especially on the software side, with new AI models and agent frameworks increasingly becoming better and more reliable. Even the no-code platforms are more powerful than couple of months back, so this is a right time to get your feet wet and run some experiments.

What are AI agents?

An AI agent can in itself act autonomously in an environment. Can take information from its surroundings, make effective decisions based on that data, and act to transform those circumstances—physical, digital, or mixed. More advanced systems can self-learn and improvise their behavior over time, constantly trying out for new solutions to a problem until the goal is achieved.

Components of an AI agent system

AI agents have different components that make up their software, each with its unique capabilities.

Sensors let the agent sense its surroundings to gather percepts (inputs from the realistic world: images, sounds, radio frequencies, etc.). These sensors can be cameras, microphones, or antennae, among other things. For software agents, it can be a web crawl function or a tool to read files.

Actuators help the agent work in the realistic world. These can be wheels, robotic arms, or a tool to create files in a computer. – Yes, you are thinking of Telsa FSD.

Processors, control systems, and decision-making mechanisms compose the “brain” of the agent. They process information from the sensors, brainstorm the best course of action, and issue commands to the actuators.

Learning and knowledge base systems store data that help the AI agent complete tasks; for example, a database of facts or past percepts, difficulties faced, and solutions captured.

AI Agents for Developers

Code Generation: AI can help generate code snippets based on the developer’s requirements or even create entire skeletons for applications.
Code Review: AI agents can review code to identify potential bugs, optimize performance, and ensure best practices are followed.
Debugging: They can analyze code to find errors and suggest possible fixes, reducing the time spent on troubleshooting.
Documentation: Automatically generate documentation for code, making it easier for developers to maintain and understand over time.
Learning Resources: Provide personalized recommendations for learning new technologies or improving existing skills.
Project Management: Integrate with project management tools to track progress, manage tasks, and ensure timely delivery.
Testing: Assist in writing and running automated tests to ensure code quality and reliability.
Version Control: Help manage version control by automating merges, handling conflicts, and tracking changes.

Examples of AI Agents for Developers

GitHub Copilot: An AI pair programmer that offers code suggestions in real-time.
Tabnine: AI code completion tool that supports various programming languages.
DeepCode: Analyzes code to identify errors and potential improvements.
Kite: Provides predictive code completions to speed up the coding process.

General-Purpose AI Agent Apps

Relevance AI: A no-code platform that allows you to build AI agents for business tasks like data processing and API calls.
Zapier: Connects your favorite apps and automates repetitive tasks with ease, offering over 6,000 app integrations.
Microsoft Power Automate: Enables you to automate workflows by connecting your apps and services.
Otter.ai: An AI-powered transcription service that can capture and share meeting notes with ease1.
Copilot X: Leverages GPT models to autonomously complete tasks by breaking them down into subtasks.

What’s In the News?

For the first time in your life, you would to be working with a CEO AI Agent, a Manager AI Agent, a Peer AI Agent.

Take this example: Think of Siri/Alexa asking you for an update and reminding you of pending tasks.

There is a real possibility that this time you might end up reporting to a non-human manager.

Recent news: “Salesforce CEO Marc Benioff said at the World Economic Forum in Davos that today’s cohort of CEOs will be the last to lead all-human workforces. The AI agents are here—and they’re taking over more work at the office.”

Source: https://fortune.com/2025/01/24/marc-benioff-salesforce-human-workforces-ai-agents/

Will AI Agents Take Our Jobs?

I cannot think of ending this article without this question answered. This technology will absolutely displace jobs and bring substantial change to the market in a very near future. Human workers may be replaced by AI agents in multiple industries. And also, more positions for AI development and maintenance would be created, along with human-in-the-loop positions, to ensure human decisions drive AI actions and not the other way around. That’s going to be game forward.

Article Written by Krishnam Raju Bhupathiraju.

The post AI Agents – The Future of Workforce appeared first on Creospan.