Step 3 of 6
Write a Useful Step
Create a step document that matches the manifest, teaches one meaningful action, and ends with an observable checkpoint.
Place step documents under content/guide-steps/your-guide-slug/. The metadata connects each document to its overview and controls its position.
---
title: Connect and Invoke
description: Connect the client, inspect the advertised tools, and invoke one tool with a valid argument.
contentType: guide-step
section: build
guideSlug: build-a-useful-mcp-client
guideStepId: connect-and-invoke
guideStepOrder: 2
authors: [Your Name]
status: draft
tags: [guide-step, client, typescript]
updatedAt: 2026-08-31
difficulty: beginner
estimatedMinutes: 35
specVersion: 2025-11-25
lastVerified: 2026-08-31
---Use standard Markdown first
Ordinary Markdown keeps contributions readable in GitHub and portable outside the site. Writers can use:
- second- and third-level headings
- bold and emphasis
- descriptive links
- ordered and unordered lists
- inline
code - fenced code blocks with a language
- blockquotes for short quotations or principles
- tables for compact comparisons
Give the step a reliable rhythm
- Explain what the reader is about to do and why.
- Show the exact command, code, or interface action.
- Explain only the details that affect the result.
- Provide a checkpoint the reader can observe.
- Identify likely failure modes when they are consequential.
Step 3
Ready to continue?
Mark this step complete when you have finished the checks above.
Checking saved progress…