Back to blog

MCP Servers: AI Is Moving to the Frontend

Hello HaWkers, an important trend is consolidating in 2025: artificial intelligence is leaving the backend and moving to the frontend. The proof is that Angular and React have launched their own MCP Servers to help AI tools better understand and work with their frameworks.

But what are MCP Servers? Why are the main frameworks investing in this? And how does it change frontend development? Let's explore.

What Are MCP Servers

MCP (Model Context Protocol) is a protocol created by Anthropic that allows AI models to connect to external data sources and tools in a standardized way.

How It Works

Before MCP:

  • Each AI tool had its own way of integrating
  • Context limited to what was in the prompt
  • Difficult to keep information up to date

With MCP:

  • Standardized communication protocol
  • Tools can expose data in real time
  • AI accesses documentation and best practices dynamically

MCP Architecture

┌─────────────────┐
│    AI Model     │
│ (Claude, GPT)   │
└────────┬────────┘

    ┌────▼────┐
    │   MCP   │
    │ Client  │
    └────┬────┘

┌────────┴────────┐
│                 │
▼                 ▼
┌─────────┐  ┌─────────┐
│ Angular │  │  React  │
│  MCP    │  │   MCP   │
│ Server  │  │  Server │
└─────────┘  └─────────┘

Framework MCP Servers

Both Angular and React have launched official MCP servers:

Angular MCP Server

Exposed resources:

  • Updated official documentation
  • Angular best practices
  • Recommended architecture patterns
  • Signals and flow control
  • Version migration

Benefits:

  • AI understands Angular idioms
  • Suggestions follow official style guide
  • Less "React-ized" code in Angular projects

React MCP Server

Exposed resources:

  • React 19 documentation
  • Hooks patterns
  • Server Components best practices
  • Concurrent features
  • New compiler

Benefits:

  • AI updated with React 19
  • Knows Server Components
  • Avoids deprecated patterns

Feature Comparison

Feature Angular MCP React MCP
Updated docs Yes Yes
Best practices Yes Yes
Migration Yes Partial
Code examples Yes Yes
Testing patterns Yes Yes
SSR/SSG patterns Yes Yes

AI In the Browser: Beyond Backend

The migration of AI to the frontend doesn't stop at MCP Servers. Libraries are enabling ML to run directly in the browser:

Browser ML Libraries

TensorFlow.js

  • Trains and runs models in the browser
  • Uses WebGL for acceleration
  • Supports pre-trained models

Hashbrown

  • Open source framework for AI agents
  • Runs entirely in the browser
  • Requires no backend

AsterMind-ELM

  • Language models in the browser
  • Local inference
  • Data privacy

Advantages of Frontend ML

Privacy:

  • Data never leaves the device
  • Easier compliance (GDPR, CCPA)
  • More comfortable users

Latency:

  • No round-trip to server
  • Instant response
  • Better UX

Cost:

  • Less backend infrastructure
  • Natural scalability (each client processes)
  • No API costs per request

Offline:

  • Works without internet
  • Smart PWAs
  • Remote use cases

Limitations

Performance:

  • Smaller models than server
  • Depends on client hardware
  • Battery on mobile devices

Complexity:

  • More complex initial setup
  • More difficult debugging
  • Browser compatibility

Implementing AI on the Frontend

If you want to start using AI on the frontend, here are some approaches:

Approach 1: TensorFlow.js

import * as tf from '@tensorflow/tfjs';

// Load pre-trained model
const model = await tf.loadLayersModel('/models/sentiment/model.json');

// Preprocess input
function preprocessText(text) {
  // Tokenization and padding
  const tokens = tokenize(text);
  return tf.tensor2d([pad(tokens, 100)]);
}

// Make prediction
async function analyzeSentiment(text) {
  const input = preprocessText(text);
  const prediction = model.predict(input);
  const score = await prediction.data();

  return {
    positive: score[0],
    negative: score[1],
    neutral: score[2]
  };
}

// Usage
const result = await analyzeSentiment('I loved this product!');
console.log(result); // { positive: 0.92, negative: 0.03, neutral: 0.05 }

Approach 2: Web AI API (Experimental)

// Experimental API available in some browsers
if ('ai' in window) {
  const session = await window.ai.createTextSession();

  const response = await session.prompt(
    'Summarize this text in one sentence:'
  );

  console.log(response);
}

Approach 3: WebGPU for Acceleration

// Check support
if ('gpu' in navigator) {
  const adapter = await navigator.gpu.requestAdapter();
  const device = await adapter.requestDevice();

  // Use GPU for ML computation
  // Significantly faster than WebGL
}

Practical Use Cases

Where frontend AI makes the most sense:

1. Smart Autocomplete

  • Real-time contextual suggestions
  • No network latency
  • Personalized per user

2. Content Moderation

  • Filter user input before sending
  • Detect spam/toxicity locally
  • Reduce server load

3. Image Recognition

  • Classify photos before upload
  • Extract text from images (OCR)
  • Detect faces for automatic crop

4. Form Assistants

  • Semantic validation
  • Fill suggestions
  • Advanced spell checking

5. UI Personalization

  • Adapt interface based on behavior
  • Predict user's next actions
  • Optimize layouts dynamically

Integrating MCP in Your Workflow

If you use AI tools for development:

Configuration with Claude

  1. Install your framework's MCP Server
  2. Configure in Claude Desktop
  3. Your interactions will have updated context

Configuration with Cursor

  1. Enable MCP in settings
  2. Add servers for used frameworks
  3. Suggestions will be more idiomatic

The Future of Frontend with AI

The trend of AI on the frontend is just beginning:

Predictions for 2026

Larger Models:

  • WebGPU will allow more complex models
  • Small LLMs running in browser
  • Complete assistants client-side

Native APIs:

  • Browsers with built-in AI APIs
  • Chrome/Firefox with built-in models
  • W3C standardization under discussion

Intelligent Frameworks:

  • React/Vue/Angular with integrated AI
  • Components that self-optimize
  • AI-assisted debugging

Conclusion

The migration of AI to the frontend represents a fundamental change in how we build web applications. With MCP Servers from major frameworks, browser ML libraries, and new APIs emerging, frontend developers need to start familiarizing themselves with these concepts.

The future is applications that think on the client, not just the server.

If you want to understand more about how AI is transforming development, I recommend checking out another article: AI Engineering: The Hottest Profession of 2025 where you'll discover career opportunities in this area.

Let's go! 🦅

Comments (0)

This article has no comments yet 😢. Be the first! 🚀🦅

Add comments