Vefskólinn · Module 4 · Connecting to the World

Plugged in

The "Connecting to the world" guide asks you to combine data from at least two APIs and one MCP server, and to use at least one skill or write your own. The group project needs live data from at least one API too. So you need things to plug into, and I made two pages to help you find them. Each one is a wall of cards, and every card opens a short how-to. I tested everything I could, and the cards tell you when I couldn't.

Not sure which one to open? If your idea is Icelandic (weather, earthquakes, buses, Alþingi, the Icelandic language), start with Iceland. For everything else (Pokémon, films, recipes, space, Formula 1), go to the World. They work the same way, so once you can read one, you can read the other.

47 cards in 8 groups

Plugged into Iceland

Icelandic data, tools and services. Weather and earthquakes from Veðurstofan, statistics from Hagstofan, Alþingi, Strætó, the krónan, the power grid live, and Miðeind's language tools. Plus Icelandic MCP servers and skills for your agent.

  • Veðurstofa
  • Hagstofa
  • Alþingi
  • apis.is
  • Strætó
  • Málstaður

Best if your topic lives in Iceland, or you want to work with Icelandic text.

Open the Iceland page

126 cards in 19 groups

Plugged into the World

The APIs people all over the world build pet projects with, the MCP servers and skills the rest of the world uses, and a red group of famous tutorial APIs that are gone. Pick the topic from your "Accessibility" page and it shows you what fits.

  • PokeAPI
  • TMDB
  • TheMealDB
  • NASA
  • Open-Meteo
  • Formula 1

Best if your topic is games, films, food, books, space, sport, or anything not Icelandic.

Open the World page

Three things to know before you pick

  1. Look at the label first

    Works in the browser means you can fetch it straight from React. Needs a server means the browser will stop you with a red CORS message. Nothing is broken when you see it. You already know the fix from Module 3: your server fetches the data, and your page fetches from your server.

  2. Keys live on the server

    If an API needs a key, it goes in .env on your server. Never in React, and never with a VITE_ or NEXT_PUBLIC_ prefix, because then it ships to every visitor. Remember the attack hour? That's how keys get found.

  3. Your agent's memory is out of date

    A lot of famous tutorial APIs are dead or have changed, and your agent learned from those tutorials. When it writes a fetch() with total confidence and nothing comes back, check the Gone group on the World page before you blame your code. It's the same skill as spotting invented APIs in the "JavaScript Frameworks" guide.

Three ways to plug in

Both pages are sorted the same way. The "Connecting to the world" guide needs the first two: at least two APIs, one MCP server and a skill. The third one is for the speciality.

Your app → the world

APIs

Your code calls fetch() and gets data back. You need at least two for the "Connecting to the world" guide, and live data from one for the group project.

Your agent → the world

MCP servers & skills For your agent

These plug into Claude Code, Codex or Copilot, not into your website, so your agent can look up real data while it helps you build. Read a skill all the way through before you use it, because it changes how your agent behaves.

The world's agents → your app

WebMCP

For the speciality: your app offers tools that browser agents can call. The MCP servers on both pages show what tools to offer, and what not to.